1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hi,
When you have nested stacks that must be rolled back to a working state, see Using ResourcesToSkip to recover a nested stacks hierarchy: see https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-continueupdaterollback.html#nested-stacks
Best,
Didier
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
Hi Didier,
The issue now is I couldn't trigger the ResourcesToSkip because it is a nested stack, and the root stack Continue to rollback option is grey out, i tried run the cli command but it seems like the resource is not being skip even though i have added the --resources-to-skip with the logical ID of that failed resource