-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
Add variable expansion to URLs for values #169
Conversation
|
|
Codecov Report
@@ Coverage Diff @@
## main #169 +/- ##
==========================================
- Coverage 84.77% 84.50% -0.28%
==========================================
Files 23 24 +1
Lines 611 626 +15
==========================================
+ Hits 518 529 +11
- Misses 93 97 +4
Continue to review full report at Codecov.
|
|
|
Hey @jmclean-starburst, is it possible that you can checkout this and test it on your setup? |
getting the below
|
Hm, it looks good in general here, because
Set |
Not sure...the error is kicked right after sops:
FWIW - i pass in the url string being surrounded by single quotes (ie
I do this because I am trying to mimic what ArgoCD passes in. |
Looks like getsops/sops#884 |
seems like the only time you leverage the expansion is via the below, which doesnt actually update the
I would have expected the |
Then, the temporary file path What happens, if you are using a invalid |
a bad token gives the below after a curl command
Then I get the:
|
This validates that the evaluation works in general. Maybe we are hitting getsops/sops#884 here. I do a commit here which introduce a workaround for that case. Otherwise, the encrypted yaml file from |
@jkroepke definitely seems like the issue is the sops tag above....i had a local |
Thanks for the feedback. Great to know that it works now.
I would like to know, if I the empty sops.yaml file is still needed, because it worked years fine without it. Before merging this, I still needs to write some documentation about this feature. |
643f487
to
5b5e5bb
Compare
5b5e5bb
to
4a61e70
Compare
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR