[Bug]: Deploying a built container on Leda / kanto-cm with databroker (without dapr)

[chheis]

What happened?

While deploying a sample application, I have observed that the ENV variables are differently used, with no clear naming.
e.g.: DAPR_GRPC_PORT => needs to be set to the databroker grpc port while using a "native" integration like in python SDK.
So it is very inconvenience that there is currently a different deployment json needed with different ENV parameters when switching between python and C++.

vehicle-app-cpp-sdk/sdk/src/sdk/grpc/VehicleDataBrokerClient.cpp

Line 56 in e060022

auto* const envPort = std::getenv("DAPR_GRPC_PORT");

Operating System

Other

What release version or branch did you use?

vehicle-app-cpp-sdk/sdk/src/sdk/grpc/VehicleDataBrokerClient.cpp

Line 56 in e060022

auto* const envPort = std::getenv("DAPR_GRPC_PORT");

Relevant log output

Connection error with grpc

Code of Conduct

• I agree to follow this project's rules for contributions

[chheis]

@doosuu: @MP91 has seen this behaviour already

[MP91]

Hey @chheis, @BjoernAtBosch is already working on a fix

[MP91]

@BjoernAtBosch isn't that already done? you adapted the environment variables or? Could you link the PR and close this?

[BjoernAtBosch]

Fixed with these versions:
https://github.com/eclipse-velocitas/devenv-runtimes/releases/tag/v1.0.3
https://github.com/eclipse-velocitas/vehicle-app-cpp-sdk/releases/tag/v0.3.3
eclipse-velocitas/vehicle-app-cpp-template@6f5705d

See SDK's README.

Corresponding PRs:
eclipse-velocitas/devenv-runtimes#22
#62
eclipse-velocitas/vehicle-app-cpp-template#56