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

git-token should be a managed secret #1

Open

tsutsu opened this issue Jan 29, 2021 · 0 comments

Labels

bug

Member

tsutsu commented Jan 29, 2021

During deploy, ensure the unsealed Secret is successfully created before proceeding to apply ReleaseTrack update.
- Can unprivileged users, who can't read Secret contents, see that the Secret exists?

tsutsu added the bug label

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