We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I have the following template:
apiVersion: v1 kind: Secret metadata: name: test stringData: ref+awsssm://test
With a value in Parameter Store in YAML format:
value1: secret value2: secret
I get the following rendered secret:
apiVersion: v1 kind: Secret metadata: name: test stringData: |- value1: secret value2: secret
I would like to give vals an hint that the value should be not handle as string, instead it just be insert as object into the existing yaml structure.
for example:
apiVersion: v1 kind: Secret metadata: name: test stringData: value1: secret value2: secret
The text was updated successfully, but these errors were encountered:
I'm also really interested in this feature. Is this part of the current roadmap?
Sorry, something went wrong.
I think this topic is already under discussion at #115. But there are no news for 2 years. #172 is also related.
No branches or pull requests
Current Behavior
When I have the following template:
With a value in Parameter Store in YAML format:
I get the following rendered secret:
I would like to give vals an hint that the value should be not handle as string, instead it just be insert as object into the existing yaml structure.
for example:
The text was updated successfully, but these errors were encountered: