cascade delete option is ticked by default , want to have it unticked by default for us.

[chiragthaker]

When you delete app in ARGOCD cascade delete option is by default ticked which can be fatal as it delete resources too from the cluster . Do anyone know how to make default untick when you delete the app from ArgoCD and then choose cascade deletion ok if we really want resources from the cluster to be deleted too.
We use apps-in-apps and want this to be disabled by default.

[resamaraschi]

Also interested in this feature. I think the default behavior should rather be removing the application from ARGO CD only. I think one wants to easily remove the whole application only in a test environment cluster and but not in a PROD cluster. Thanks

[LelandSindt]

I got bit by this today (entirely my fault for not paying attention).

May I suggest that the Cascade option be checked based on the presence/absence of

metadata:
  finalizers:
    - resources-finalizer.argocd.argoproj.io

https://argoproj.github.io/argo-cd/user-guide/app_deletion/

@lelandsindttouchnet

[keithchong]

@alexmt, should the CLI's default be changed to false as well?

[jannfis]

@alexmt, should the CLI's default be changed to false as well?

IMHO, I would wish for the CLI to behave as follows:

• If cascade is set to true, ask the user whether he really wants to delete the application and all of its resources
• For automation, either a --force or --yes option should specify to skip a dialogue like above and assume yes on the answer

However, this would be breaking change for existing automation, I guess. Maybe we could also check whether the execution environment has a pseudo terminal, and if not, skip security check dialogue and assume yes as well.

[alexmt]

I really like your suggestion @jannfis . And pseudo terminal check is a nice workaround to prevent breaking existing automation.

[keithchong]

Hi @alexmt, please assign this to me.

[jannfis]

Hi @alexmt, please assign this to me.

Done.

[keithchong]

Here is a screenshot of the new prompt. The cascade checkbox will remain checked by default.

[rbreeze]

@keithchong @chiragthaker was this fixed by #4994 ?

[alexmt]

This is fixed now. Popup message explains the danger of cascade deletion and ask user to type the app name.

[benjamin-bergia]

Hi,

sorry to come back on this but it looks like on v2.5.x this is back to the original behavior (cascade by default).
Is there any way to define on applicationsets and applications that deletion shouldn't be cascading by default in the current version? Is removing the finalizer effective and the recommended way to go? I manage my applicationsets with argocd itself so I can really pass CLI options.

[paddy667]

Adding a not here as I didn't see a solution in this thread. I had the same issue with deleting applicationsets, which would delete the ArgoCD application and in turn delete the cluster resources. Since my applicationsets are managed by ArgoCD itself, a small error with existing applicationsets could set off a chain reaction of deletion. Adding the following prevents this:

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
spec:
  syncPolicy:
    preserveResourcesOnDeletion: true