-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
♻️ changed director-v2
env var definition in compose spec by making it explicit
#4786
♻️ changed director-v2
env var definition in compose spec by making it explicit
#4786
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4786 +/- ##
========================================
+ Coverage 85.3% 86.9% +1.6%
========================================
Files 1069 1125 +56
Lines 45212 47245 +2033
Branches 683 1037 +354
========================================
+ Hits 38567 41101 +2534
+ Misses 6490 5911 -579
- Partials 155 233 +78
Flags with carried forward coverage won't be shown. Click here to find out more. |
director-v2
env var definition in compose spec by making it explicit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good. Thank you!
Code Climate has analyzed commit 47959fa and detected 0 issues on this pull request. View more on Code Climate. |
Kudos, SonarCloud Quality Gate passed!
|
What do these changes do?
New env vars need to be explicitly captured by services. As requested by ops.
NOTE: this looks like garbage, but it produces the expected result. I could not find a proper way of escaping it. @YuryHrytsuk @mrnicegyu11 any ideas? I need to have a default{}
if the env var is missing.NOTE: trying to add
{}
as a default to an env var in docker-compose.yaml will require you to do something like- ENV_VAR=${ENV_VAR:-{}
, notice the missing}
at the end. If it is added it will resolve toENV_VAR{}}
Related issue/s
dynamic-sidecar
adding support formetrics
andon_shutdown
events for user services (⚠️OPS) #4697How to test
DevOps Checklist