-
Notifications
You must be signed in to change notification settings - Fork 198
feat: allow interactive remove #4078
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
Conversation
Signed-off-by: Austin Abro <austinabro321@gmail.com>
Signed-off-by: Austin Abro <austinabro321@gmail.com>
Signed-off-by: Austin Abro <austinabro321@gmail.com>
✅ Deploy Preview for zarf-docs canceled.
|
Codecov Report❌ Patch coverage is
... and 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
Signed-off-by: Austin Abro <austinabro321@gmail.com>
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.
LGTM with style nit to match other prompt text.
Co-authored-by: Kit Patella <kit@defenseunicorns.com> Signed-off-by: Austin Abro <37223396+AustinAbro321@users.noreply.github.com>
Signed-off-by: Austin Abro <austinabro321@gmail.com>
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.
Changes look good. Noticed an odd behavior in testing - where an invalid component name used with --components
on remove resulted in the full package being removed - we should open a new issue for this.
Just chiming in here but we also experienced this issue as well using zarf v0.58.0 while trying to remove a component within a uds core package. We thought it was expected behavior so I never reported this but it did cause some issues and broke our core deployment putting it in a funky state... |
Signed-off-by: Austin Abro <austinabro321@gmail.com> Signed-off-by: Austin Abro <37223396+AustinAbro321@users.noreply.github.com> Co-authored-by: Kit Patella <kit@defenseunicorns.com> Signed-off-by: Cade Thomas <cadethomas23@gmail.com>
Description
This allows users to preform an interactive remove when
--confirm
is not set. I also added the package yaml print as I feel it could be a useful debugging tool if something went wrong during a confirmed remove. It's also consistent with our other interactive option, deploy. I don't feel super strongly either way here though.Related Issue
Fixes #3239
Checklist before merging