cloudtools/stacker

handle multiple users updating a stack at once

Open

#65 建立於 2015年8月10日

在 GitHub 查看
 (4 留言) (0 反應) (0 負責人)Python (706 star) (166 fork)batch import
enhancementhelp wantedquestion

描述

Right now there's no special logic that would stop 2 people from attempting to update stacks at the same time. In general the second attempt will see the stacks being updated, and probably do the right thing, but I can see some cases where that wouldn't happen and could leave stacks in invalid states.

So - probably worth having some way to lock the stack while you're working on it. Not sure where that would be handled.

貢獻者指南

技術棧
python
領域
infrastructurecloudbackend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
PythonAWS CloudFormationbasic concurrency concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
The issue proposes adding a lock to prevent concurrent stack updates. First, examine the current update process in the stacker codebase, focusing on files like `stacker/actions/base.py` or similar. Look for any existing concurrency handling. Then, consider implementing a database level lock using a table with stack names and a lock state, or using AWS DynamoDB with conditional writes. Also, review the issue comments for any suggestions. The solution should ensure that only one update per stack can run at a time, and handle timeouts or failures gracefully.