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

feat: use build env file to load secret environs dynamically #61

Merged
merged 4 commits into from
Nov 7, 2022

Conversation

floralatin
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented Nov 4, 2022

Codecov Report

Merging #61 (f3a53f0) into main (b4d1131) will increase coverage by 1.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #61      +/-   ##
==========================================
+ Coverage   82.35%   83.43%   +1.08%     
==========================================
  Files           5        5              
  Lines         153      163      +10     
==========================================
+ Hits          126      136      +10     
  Misses         27       27              
Impacted Files Coverage Δ
normalizer/docker/parser.py 94.49% <100.00%> (+0.55%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

normalizer/docker/parser.py Outdated Show resolved Hide resolved
@floralatin floralatin changed the title feat: use build env path to load secret environs dynamically feat: use build env file to load secret environs dynamically Nov 4, 2022
@floralatin floralatin merged commit 0d2e5df into main Nov 7, 2022
@floralatin floralatin deleted the refactor-build-env branch November 7, 2022 03:26
@nan-wang
Copy link
Member

nan-wang commented Nov 7, 2022

🎉 This PR is included in version 0.10.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants