Enforce unique CloudFormation stack names
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- aws, typescript
- 领域
- devops
调研方向
Start by finding where the reusable workflows in apify/workflows construct or accept CloudFormation stack names before deployment, and where a validation step could be inserted (likely a workflow step or a script invoked by it). Note the open design questions in the issue (environment naming scheme, legacy-stack opt-out, name->account mapping) — a decision from a maintainer is needed before implementation. Done looks like: new stacks are rejected unless the name is prefixed with the deploying repo and is unique in the repository, while legacy names remain deployable via an opt-out.
由索引模型根据 Issue 内容生成。
描述
NOTE: this could be a good first task for a new DevOps engineer.
To prevent issues with overriding CloudFormation stacks because of a naming conflict, we need to ensure that the CloudFormation stacks have unique names.
This would be hard to enforce directly across the whole GitHub organizations, but we can split it into two parts:
- make sure that the stack names are prefixed with the repo that is trying to deploy them
- make sure that the stack names are unique in the repository
We could even make sure that the stack names contain the environment that they're being deployed to, and that they're being deployed to the right environment according to the name.
So there would be stack names like:
apify-core-org-s3-bucketsapify-web-member-iam-roles
TBD: should the environments be called org and member, or org, prod and staging?
Unfortunately, CloudFormation doesn't let you rename existing stacks, so we'll have to have some option to opt-out of these names for legacy stacks. We should not allow new stacks to be created with the wrong names, though. Maybe, if the legacy stack name is in the wrong format and the repo and account can't be inferred automatically, we could even have a mapping of stack name -> repo & AWS account that would verify that the stacks are being deployed to the correct account.
- 主要语言
- TypeScript
- 星标
- 15
- 派生
- 7
- 平均合并
- 1 天 16 小时
- 30 天内合并 PR
- 5
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apify/workflows 的其他 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 77/100
TomerAberbach/profiler-md#733 ·
维护者通常 1 天内回复
-
bug priority: medium
难度 2/5 1-3 小时 新手友好度 68/100
brentspine/brents-toasts#143 ·
-
🐛 bug 🗺️ DB Models & Ops
难度 2/5 1-3 小时 新手友好度 83/100
LibreChat-AI/LibreChat#17214 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
Wavvon/Wavvon-clients#136 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
umami-software/umami#4637 ·
维护者通常 3 天内回复