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

Feature: Support complex values #205

Open
jkroepke opened this issue Feb 10, 2024 · 0 comments
Open

Feature: Support complex values #205

jkroepke opened this issue Feb 10, 2024 · 0 comments

Comments

@jkroepke
Copy link
Contributor

Current Behavior

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
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

No branches or pull requests

1 participant