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

fix: detect duplicate env files between CLI and Compose #49

Merged
merged 1 commit into from
Sep 28, 2024

Conversation

aksiksi
Copy link
Owner

@aksiksi aksiksi commented Sep 26, 2024

No description provided.

Copy link

codecov bot commented Sep 26, 2024

Codecov Report

Attention: Patch coverage is 80.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 73.17%. Comparing base (6cb9e5f) to head (c5ae726).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
compose.go 80.00% 1 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #49      +/-   ##
==========================================
+ Coverage   73.03%   73.17%   +0.14%     
==========================================
  Files           6        6              
  Lines         749      753       +4     
==========================================
+ Hits          547      551       +4     
  Misses        163      163              
  Partials       39       39              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@aksiksi aksiksi marked this pull request as ready for review September 28, 2024 15:05
If the same env file is passed via CLI and set in the Compose `env_file`
for a service, then we do not want to include the env file twice.

To achieve this, we map the CLI env files into absolute paths to ensure
that we can compare them with env_file entries returned by the Compose
library.
@aksiksi aksiksi merged commit fed9565 into main Sep 28, 2024
6 checks passed
@aksiksi aksiksi deleted the duplicate-env-file branch September 28, 2024 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant