Fails to delete resources when deletion protection is enabled.

[wakeful]

Hey,

Currently, cloud-nuke fails if a resource it is trying to delete has "deletion protection" enabled. This feature is available across various resources such as DynamoDB, RDS, load balancers, and others.

What’s your opinion on extending the logic to allow cloud-nuke to disable "deletion protection" and retry the deletion? Or do you think this flag should be removed outside of the nuke process?

[james03160927]

This is an interesting suggestion. Typically, users would rely on cloud-nuke to clean up resources left over from testing or those no longer needed, regardless of their settings. Therefore, it makes sense to delete such resources with a retry mechanism, even if deletion protection is enabled.

[wakeful]

Typically, users would rely on cloud-nuke to clean up resources left over from testing or those no longer needed, regardless of their settings. Therefore, it makes sense to delete such resources with a retry mechanism, even if deletion protection is enabled.

Exactly, I have the same feeling. However, since this would be a change in behaviour, we could add an extra option to preserve the current behaviour.

Let me create an initial PoC pull request with the changes, and we can discuss it in more detail.

[james03160927]

SGTM. Thanks!

[james03160927]

Friendly ping on this @wakeful