1 個回答
- 最新
- 最多得票
- 最多評論
0
Okay, so this place is absolutely dead.
I ended up taking a chance and deleted the Beanstalk environment within the AWS Console. I had to do that since CloudFormation never tried to delete the environment again after the initial attempt. I am disappointed that there is no retry mechanism when the solution is so obvious, but I guess that's just one of the many quirks of CloudFormation. Yes, it was my own mistake that caused me to end up in that situation, but I hoped and expected CFM to handle it a bit more gracefully instead of just getting stuck indefinitely. Disappointing!
So delete the environment manually and CFM will "understand" this and proceed with the stack update afterwards. At least that's what happened for me.
已回答 2 年前
相關內容
- 已提問 6 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 8 個月前
- AWS 官方已更新 9 個月前
- AWS 官方已更新 3 個月前