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.

Sign up for GitHub

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

Jump to bottom

feat: add optional KUBECONFIG_BASE64 env to pass base64-encoded value #39

Open

shivanshs9 wants to merge 1 commit into deliverybot:master from shivanshs9:base64-support

shivanshs9 commented Sep 4, 2020

Changes:

Added a parseBase64 function to decode base64 secret value of KUBECONFIG_BASE64 env
If the user hasn't set KUBECONFIG_FILE env, then try to decode KUBECONFIG_BASE64 env value.

Motivation:

To make our workflow compliant with other github actions, we stored base64-encoded value of kubeconfig.
Decoding it in a previous step and setting is as env or output of step doesn't work since GitHub Actions truncates multi-line strings.
Decoding the secret from base64 and then encoding it to Github Actions compliant string didn't work since now Helm cannot parse the yaml.


          feat: add optional KUBECONFIG_BASE64 env to pass base64-encoded value

8a27a27

LennardWesterveld mentioned this pull request

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet