Right now, user’s env (passed with commands) are overriding default env (the one in the
The problem is user’s env should be considered as sensitive data (cannot be exposed publicly). So, we cannot add them in the protobuf service definition.
One solution will be to no override the default env but simply to have a dedicated arrays to store them outside the service definition (as “metadata”).
Like this, the service definition will holds the default env defined by the mesg.yml that can be exposed to the network.
do not override default env with user’s in
store user’s env somewhere
add envs to
do the mapping from dependency proto to service
[dependant on #860] add envs to
- [dependant on #860] do the mapping from dependency proto to service