cloudtools/stacker

handle multiple users updating a stack at once

Open

#65 opened on 2015年8月10日

GitHub で見る
 (4 comments) (0 reactions) (0 assignees)Python (706 stars) (166 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.