You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what should be investigated or refactored
We've gotten reports from the community that zarf package remove can leave behind orphaned state and occasionally has unexpected behavior. Before adding new features to the operation, we should investigate how it handles existing resources, potential issues like slowdowns, timeouts, and retries, and how complete it is at cleaning up an existing package deployment.
While verifying the behavior of the remove operation, there's a good opportunity to add in quality of life improvements like debug logging (with duration) and additional doc comments on exported fields (like usage info on the options struct).
Describe what should be investigated or refactored
We've gotten reports from the community that
zarf package remove
can leave behind orphaned state and occasionally has unexpected behavior. Before adding new features to the operation, we should investigate how it handles existing resources, potential issues like slowdowns, timeouts, and retries, and how complete it is at cleaning up an existing package deployment.Links to any relevant code
Docs
zarf/site/src/content/docs/commands/zarf_package_remove.md
Line 15 in 36c06e2
Cmd
zarf/src/cmd/package.go
Lines 659 to 710 in 36c06e2
Packager2 remove
https://github.com/zarf-dev/zarf/blob/main/src/internal/packager2/remove.go#L36-L167
og packager remove
https://github.com/zarf-dev/zarf/blob/main/src/pkg/packager/remove.go#L33
Additional context
While verifying the behavior of the remove operation, there's a good opportunity to add in quality of life improvements like debug logging (with duration) and additional doc comments on exported fields (like usage info on the options struct).
Relates to:
#3525
The text was updated successfully, but these errors were encountered: