-
Notifications
You must be signed in to change notification settings - Fork 172
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
Zarf CLI should easily show Git and Registry credentials #1098
Comments
I am still on an older Zarf, but from what I can tell, the stored secrets did not have all of the credentials. I think notably, either the git or registry read/write user were not published as a secret. Just wanted to ask the question to see if this mechanism would encompass all creds. |
@jtaylor-afs yep, in newer versions of Zarf all credentials are stored in the zarf state. Here is an example of the output from the commend @runyontr posted from a local dev run (keys have been rotated):
|
## Description Add command to easily get credentials printed during zarf init (i.e. git, logging, registry) ## Related Issue Fixes #1098 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [ ] Test, docs, adr added or updated as needed - [ ] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed
## Description Add command to easily get credentials printed during zarf init (i.e. git, logging, registry) ## Related Issue Fixes #1098 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [ ] Test, docs, adr added or updated as needed - [ ] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed
When looking to debug a deployment after doing a zarf init, if I didn't save the login credentials that get spit out durin gthe init phase, I can't find a clean way to discover the credentials. This is how I've been finding it:
it would be nice if there were a zarf cli command to extract either the full secret, or at least the credentials that were returned as part of the init phase
The text was updated successfully, but these errors were encountered: