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

error out if users try to change Zarf deployed services credentials on re-init #3189

Open
AustinAbro321 opened this issue Nov 5, 2024 · 0 comments
Labels
enhancement ✨ New feature or request

Comments

@AustinAbro321
Copy link
Contributor

Is your feature request related to a problem? Please describe.

When a user attempts to update the credentials of Zarf-deployed service using zarf init and flags such as --artifact-*, --registry-*, or `--git- with values different from the existing ones, they receive a warning that these services cannot be updated during a re-init. Instead of ignoring these flags, we should require users to execute the command with flags that are not ignored.

Describe the solution you'd like

  • Given I have a cluster already initialized with a registry pull password of "original-value"
  • When I run zarf init --registry-pull-password="new-value"
  • Then Zarf errors out immediately and tells me to use zarf tools update-creds

Describe alternatives you've considered

One alternative to consider would be actually allowing the credentials to be changed on re-init. IMO better to keep things simple for now and keep these commands separate, even if we implemented this issue, we could always change to allowing in the future if users ask for it.

@AustinAbro321 AustinAbro321 added the enhancement ✨ New feature or request label Nov 5, 2024
@github-project-automation github-project-automation bot moved this to Triage in Zarf Nov 5, 2024
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
Status: Triage
Development

No branches or pull requests

1 participant