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
If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
A clear and concise description of what the bug is.
To Reproduce
Set up argocd
create an application confusingly called applications
Point it to a folder that includes the argocd application (so that argocd is managed as an application like everything else)
Add other applications
Enable show orphaned and check it
Add other applications
Wait ~18 months for a new dev to come along and decide "What is this Applications thing?" and choose to delete it.
Expected behavior
If an Application's ownership chain can be traced to owning the application that owns the running argocd, argocd should vehemently protest when asked to delete it.
Screenshots
I can draw a blank screen...
For simplicity, please accept this in lieu of a screenshot:
😭
Here's a picture of the Applications object looking confused at itself:
At the very least, it'd be nice if ArgoCD were able to recognize that this "unmanaged" object is in fact the object itself and not pretend it's some unknown object.
Version
I'm not entirely certain, ArgoCD deleted itself, so I don't have the version handy.
It could really be solved if argocd supported a "deletion protection" flag, similar to the AWS EC2's instance "termination protection" flag that prevents any kind of deletion, be it automated or manual, until the flag is explicitly set to false in the object definition.
If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
Checklist:
argocd version
.Describe the bug
A clear and concise description of what the bug is.
To Reproduce
applications
show orphaned
and check itApplications
thing?" and choose to delete it.Expected behavior
If an Application's ownership chain can be traced to owning the application that owns the running argocd, argocd should vehemently protest when asked to delete it.
Screenshots
I can draw a blank screen...
For simplicity, please accept this in lieu of a screenshot:
😭
Here's a picture of the Applications object looking confused at itself:
At the very least, it'd be nice if ArgoCD were able to recognize that this "unmanaged" object is in fact the object itself and not pretend it's some unknown object.
Version
I'm not entirely certain, ArgoCD deleted itself, so I don't have the version handy.
Logs
I can actually retrieve these if someone thinks ArgoCD did protest and they question my recreation of the steps.
The text was updated successfully, but these errors were encountered: