-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update permissions for kubectl.config.yaml #710
Update permissions for kubectl.config.yaml #710
Conversation
the reason we never saw this is because we started using ArgoCD (which we use helm template render) before the switch to helm v3, so this code was never later used with helm v3 except I think just by your project. |
Co-authored-by: Andy Thompson <me@andytson.com>
Co-authored-by: Andy Thompson <me@andytson.com>
@@ -87,7 +87,7 @@ command('app deploy <environment>'): | |||
#!bash(harness:/helm)|= | |||
set -o pipefail | |||
cd "${ENVIRONMENT}" | |||
doctl -t "$DO_ACCESS_TOKEN" kubernetes cluster kubeconfig show "$CLUSTER" > kubectl.config.yaml | |||
(umask 0077 && doctl -t "$DO_ACCESS_TOKEN" kubernetes cluster kubeconfig show "$CLUSTER" > kubectl.config.yaml) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the record: umask
removes the bits that are allowed on a file on creation, so e.g. 0007 means if a file created with 666 permissions then it gets 660 permissions. You can see it easily with (umask 0077 && touch testfile) that it gets 600 permissions.
Description
After upgrading to helm 3, I faced this issue and I found a potential solution for this too: helm/helm#9115