-
Notifications
You must be signed in to change notification settings - Fork 199
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
Output as a string does not interpolate secrets #434
Comments
@tprobinson thanks for reporting. Currently, refs/secrets are designed to be used only from the inventory. Manipulation of these objects via an input will result in undefined behavior as you are describing. |
@tprobinson and now that I had a better second look at this, you're right, this should not be happening. Thanks again, will review. |
@tprobinson this is fixed, let me know if that works for you as well. Thank you |
I'm trying to test this, but I can't seem to compile the binary myself. I'm not much of a Python dev so I'm probably doing something wrong, but running via the Dockerfile build gets me this:
Adding
|
Describe the bug/feature
Using 0.26.0, when a jsonnet component outputs a string and not an object, secret references remain uninterpolated unless
kapitan reveal
is run.To Reproduce
Steps to reproduce the behavior:
Create files in a new Kapitan project as seen in https://github.com/tprobinson/kapitan-issue-demonstration
Run
kapitan compile
.Expected behavior
Secrets should be interpolated in the final output.
Additional context
If secrets are interpolated by walking the object that's output by jsonnet, this may be difficult. On a related note, the
?{ ... }
secret references get mangled when attempting to operate on them with functions like url encoding. If the secrets' actual value were passed in to jsonnet instead of just strings containing the?{ ... }
references, that may solve two issues at once.The text was updated successfully, but these errors were encountered: