Closed zaro0508 closed 3 years ago
Obviously this a terrible error message. Happens when there are no stacks recognised to act on and our thread pool for executing is 0.
Would you be able to post a demo stack of this so we can try and trace why this wouldn't work for delete?
will do @ngfgrant
hmm, I can't seem to reproduce this issue with a simple sceptre project. My real project uses sceptre resolvers and hooks which might be causing the problem. Unfortunately that's not real easy for me to test.
The command that generated this error uses the greedy pattern matching feature that was in ver 2.3 but was removed (in PR #731) for ver 2.4. I suspect that this error is due to using greedy pattern match. However since it has been removed in ver 2.4 we probably won't see it anymore.
Execute sceptre delete with
ignore-dependencies
flag causes a "ValueError: max_workers must be greater than 0". The exact command works fine when theignore-dependencies
flag is not used.Environment is Python 3.6.3 and Sceptre 2.3.0
working exeuction
Failing execution: