Closed pcrespov closed 3 months ago
Attention: Patch coverage is 93.75000%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 88.5%. Comparing base (
cafbf96
) to head (eb42cc4
). Report is 290 commits behind head on master.
that is very nice! thanks! Now regarding your question, I think for example in s4l the variables are probably needed in the core service which I do not think is the main one. but @mguidon can enlighten us
If that is the case, I do not have the info to know which service is "the core" service
Very nice, thanks!
Minor thought on the name of the variable
OSPARC_NODE_ID
: I guess in the code you normally say "node" and this word is mostly used by devs. For user-facing docs, etc... we tend to use more "Service". But I assume users who will use this envs are enough dev-oriented to understand what that variable represent. 😉
@elisabettai Unfortunately this is already decided and used in the client side. Can you perhaps follow up with a small entry in the manual at some time? Not urgent
What do these changes do?
Injects automatically
to all services in a dynamic-service compose. I.e. all dynamic services get automatically access to these environs. NOTE that the key/secrets are customised per user.
@sanderegg @mguidon should we only inject in the "main" service, i.e. the one specified by
simcore.service.container-http-entrypoint
?Related issue/s
How to test
services/director-v2/tests/unit/test_modules_osparc_variables.py
printenv | sort | grep OSPARC_
and check that all the env-vars above are defined ![Uploading image.png…]()Dev-ops checklist