Delete change sets fails if any stack is not created
alex-harvey-z3q opened this issue · 0 comments
alex-harvey-z3q commented
Subject of the issue
A scenario in a stack group may exist such as the following:
Your environment
- version of sceptre (sceptre --version) latest
- version of python (python --version) 3.10
- which OS/distro Ubuntu
Steps to reproduce
% sceptre status network.yaml·
{
"direct-connect": "PENDING", // NOTE STACK DELETED OR NOT CREATED
"vpc": "CREATE_COMPLETE",
"nacl": "CREATE_COMPLETE",
"network": "CREATE_COMPLETE"
}
% sceptre list stacks network.yaml
---
direct-connect.yaml: test-e2e-direct-connect
nacl.yaml: test-e2e-nacl
network.yaml: test-e2e-network
vpc.yaml: test-e2e-vpc
% sceptre delete -y network.yaml sceptre-network
The Change Set will be delete on the following stacks, if applicable:
network
"An error occurred (ValidationError) when calling the DeleteChangeSet operation: Stack [test-e2e-direct-connect] does not exist"
Expected behaviour
Sceptre should try to delete change sets for the existing stacks and simply print a warning that the missing stack does not exist.
Actual behaviour
An exception is raised and no change sets are deleted.