Dependabot encountered the following error when parsing your .dependabot/config.yaml:

The property '#/update_configs/0/package_manager' value "rust" did not match one of the following values: javascript, ruby:bundler, php:composer, java:maven, elixir:hex, rust:cargo, java:gradle, dotnet:nuget, go:dep, go:modules, docker, elm, submodules, github_actions, python, terraform
The property '#/update_configs/1/package_manager' value "rust" did not match one of the following values: javascript, ruby:bundler, php:composer, java:maven, elixir:hex, rust:cargo, java:gradle, dotnet:nuget, go:dep, go:modules, docker, elm, submodules, github_actions, python, terraform

Please update the config file to conform with Dependabot's specification using our docs and online validator.

Dependabot couldn't find a Cargo.toml for this project.

Dependabot requires a Cargo.toml to evaluate your project's current Rust dependencies. It had expected to find one at the path: /fortuneservice/Cargo.toml.

If this isn't a Rust project, or if it is a library, you may wish to disable updates for it in the .dependabot/config.yaml file in this repo.

View the update logs.

Add health check for fortuneservice currently commented out in k8s yaml. Should probably be based on https://github.com/grpc-ecosystem/grpc-health-probe

Every code change builds the docker image without any cache. Probably look at having a base image which has a default setup of packages compiled?

The base image based on Debian is over 1 gb. Should look at Alpine, which has rust as a package (even though it is old).

Dependabot couldn't parse the config file at .dependabot/config.yaml. The error raised was:

(<unknown>): did not find expected key while parsing a block mapping at line 6 column 5

Please ensure the config file is a valid YAML file. An online YAML linter is available here.

The kubernetes that we get using docker-for-desktop provides a loadbalancer when we specify it in yaml. So we don't need metallb on OSX (Mac) when the kube context is docker-for-desktop or docker-desktop.

Currently there is an error at the end of skaffold run when using docker-for-desktop cluster. We need to fix this (the setup works inspite of the error, but I guess it is confusing to the user)

Dependabot couldn't find a Cargo.toml for this project.

Dependabot requires a Cargo.toml to evaluate your project's current Rust dependencies. It had expected to find one at the path: /fortuneservice/Cargo.toml.

If this isn't a Rust project, or if it is a library, you may wish to disable updates for it in the .dependabot/config.yaml file in this repo.

View the update logs.

Dependabot couldn't find a Cargo.toml for this project.

Dependabot requires a Cargo.toml to evaluate your project's current Rust dependencies. It had expected to find one at the path: /fortuneservice/Cargo.toml.

If this isn't a Rust project, or if it is a library, you may wish to disable updates for it in the .dependabot/config.yaml file in this repo.

View the update logs.

Hi! I was looking at a microservices demo exactly as yours for Rust and I noticed Distributed (open) tracing - partially done but it wasn't exactly clear the status of it or what means partially done. What's in it and what's missing? Honest question out of curiosity :-)

Dependabot couldn't find a Cargo.toml for this project.

Dependabot requires a Cargo.toml to evaluate your project's current Rust dependencies. It had expected to find one at the path: /fortuneservice/Cargo.toml.

If this isn't a Rust project, or if it is a library, you may wish to disable updates for it in the .dependabot/config.yaml file in this repo.

View the update logs.

We should use a proper dns resolution crate/solution instead of the ugly code with getent in frontend service. If we use a crate, it should use async/await syntax and based on tokio.