I experienced the issues described in #28 for a disk attached to a VM. The delete operation failed to delete the VM disk.
I opened a support case to discuss the issue, but more importantly to understand exactly which resource types may create resources implicitly and not be deleted by a stack deletion operation. I see #70 was created to track resources but then later it was decided to open individual tickets for each discovery.
In my current engagement we use a lot of different resource types, and I just wanted to check that none would be affected by these deletion limitations before diving into a more detailed proof of concept work.
Is there a known list of affected resource types? I think it would be useful to include some documentation\guidance so users are aware of this limitation and it might also serve to reduce support cases on the same.
I experienced the issues described in #28 for a disk attached to a VM. The delete operation failed to delete the VM disk.
I opened a support case to discuss the issue, but more importantly to understand exactly which resource types may create resources implicitly and not be deleted by a stack deletion operation. I see #70 was created to track resources but then later it was decided to open individual tickets for each discovery.
In my current engagement we use a lot of different resource types, and I just wanted to check that none would be affected by these deletion limitations before diving into a more detailed proof of concept work.
Is there a known list of affected resource types? I think it would be useful to include some documentation\guidance so users are aware of this limitation and it might also serve to reduce support cases on the same.