Skip to content
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

Merged
merged 13 commits into from
Oct 2, 2023

Conversation

GitHK
Copy link
Contributor

@GitHK GitHK commented Sep 22, 2023

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 to ENV_VAR{}}

Related issue/s

How to test

DevOps Checklist

@GitHK GitHK self-assigned this Sep 22, 2023
@codecov
Copy link

codecov bot commented Sep 22, 2023

Codecov Report

Merging #4786 (47959fa) into master (a13e39c) will increase coverage by 1.6%.
The diff coverage is n/a.

Impacted file tree graph

@@           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     
Flag Coverage Δ
integrationtests 65.1% <ø> (+<0.1%) ⬆️
unittests 84.7% <ø> (-0.2%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 175 files with indirect coverage changes

@GitHK GitHK added this to the the nameless milestone Sep 22, 2023
@GitHK GitHK added the t:maintenance Some planned maintenance work label Sep 22, 2023
@GitHK GitHK changed the title ♻️ env var definition refactor ♻️ changed director-v2 env var definition in compose spec by making it explicit Sep 22, 2023
@GitHK GitHK marked this pull request as ready for review September 25, 2023 11:22
@GitHK GitHK enabled auto-merge (squash) September 25, 2023 14:01
Copy link
Contributor

@YuryHrytsuk YuryHrytsuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good. Thank you!

@codeclimate
Copy link

codeclimate bot commented Oct 2, 2023

Code Climate has analyzed commit 47959fa and detected 0 issues on this pull request.

View more on Code Climate.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 2, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.2% 0.2% Duplication

@GitHK GitHK merged commit 3c742bb into ITISFoundation:master Oct 2, 2023
@matusdrobuliak66 matusdrobuliak66 mentioned this pull request Oct 5, 2023
36 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:maintenance Some planned maintenance work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants