Closed gcasilva closed 11 months ago
Hey @gcasilva - thanks for reporting this.
Looks like we're not using a waiter here. This should be a straight forward fix.
This will be really useful for our use case too. Any ETA?
@andrew-glenn I was able to implement the fix for this and added a new PR for it if you can please review/approve it. https://github.com/aws-ia/taskcat/pull/811
I consider this issue now resolved. Please re-open if this resurfaces.
Describe the bug A clear and concise description of what the bug is. Taskcat test clean command should return that the cloudformation template has been deleted only after Cloudformation deletion has completed. This causes issues when you execute taskcat test run command again afterwards in a shell script for example as you can run into racing conditions where the new taskcat test won't be able to be completed because previous resources that shouldn't exist are conflicting since they haven't been deleted by Cloudformation completely yet. Only solution is to create sleep timers in your shell script, which isn't optimal as one needs to know how long it takes for the cloudformation template to complete.
To Reproduce Steps to reproduce the behavior:
aws configure
? noExpected behavior A clear and concise description of what you expected to happen. Taskcat test clean command should return that the cloudformation template has been deleted only after Cloudformation deletion has completed.
Screenshots If applicable, add screenshots to help explain your problem.
**Version (Please make sure you are running the latest version of taskcat)
Taskcat Version (ex: [2018.817.210357]) 0.9.40
Note: Python Version (python3 required) Python 3.9.6
To find versions: Via taskcat:
taskcat -V
Via pip3:pip3 show taskcat
Note: both version should match
To update taskcat run: for docker :
docker pull taskcat/taskcat
for pip3:pip3 install --upgrade taskcat
Additional context Add any other context about the problem here.