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.