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

Add possibility to decode base64 encoded parameters that are needed in clear text #236

Open
henninggross opened this issue Mar 18, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@henninggross
Copy link
Member

Issue

There are cases where one needs to have a multiline value (e.g. a certificate or a RSA key) in their template in clear text.

See this example (where TLS_CERTIFICATE and TLS_PRIVATE_KEY should be multiline values):

- apiVersion: route.openshift.io/v1
 kind: Route
...
 tls:
    certificate: ${TLS_CERTIFICATE}
    insecureEdgeTerminationPolicy: Redirect
    termination: edge
    key: ${TLS_PRIVATE_KEY}

When one now wants to add a key or a certificate to his .env.enc file he needs to base64 encode them and add a suffix to the parameter like this:
TLS_CERTIFICATE.B64=BASE_64_ENCODED_VALUE

This results in Tailor adding the base64 encoded value to the OpenShift template, which is not what one wants to happen with such parameters.

Possible Solution

A possible solution might be to introduce a suffix like .B64DECODE that tells Tailor to take the base64 encoded value and decode it before adding it to the template.

@henninggross henninggross added the enhancement New feature or request label Mar 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant