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
Triggering deletion of app as appset item with "non-cascading" option selected - leads to cascading deletion
To Reproduce
Create app of appsets with appset containing other apps
Navigate to app of appsets
Delete appset child application by pressing menu with three dots, "delete", "non-cascading", "ok" (or by clicking on application and pressing "delete", "non-cascading", "ok")
See that application resources are also deleted with application
Important: this behavior cannot be reproduced when deleting application which is not appset child application (e.g. standalone application in app of apps)
Expected behavior
Application resources aren't deleted with application, because UI offers non-cascading deletion in this case. UI should not mislead users
Screenshots
Version
2.12.3
The text was updated successfully, but these errors were encountered:
Delete is exclusive for Application, and DeleteResource is used for any resources (including Application), and the meaning of "non-cascading" is different from each other.
"non-cascading" in Delete: The resources identified by tracking label are left orphaned.
@mikutas that's exactly correct! I think maybe we should have a special UI for DeleteResource when deleting an Application to help the user understand the cascade options
Checklist:
argocd version
.Describe the bug
Triggering deletion of app as appset item with "non-cascading" option selected - leads to cascading deletion
To Reproduce
Important: this behavior cannot be reproduced when deleting application which is not appset child application (e.g. standalone application in app of apps)
Expected behavior
Application resources aren't deleted with application, because UI offers non-cascading deletion in this case. UI should not mislead users
Screenshots
Version
The text was updated successfully, but these errors were encountered: