Correct development target Terraform owner metadata
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 50/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python
- 领域
- devops, infrastructure
调研方向
The mislabeled value is terraform_root for the website-development target in deploy/deployment_targets.py, around line 533, which currently reads main/website and should read main/dev. Leave the production target's main/website root and all target, account, region, secret and image guards unchanged. Find the existing contract tests that cover this metadata and run them; done means the development target reports main/dev, production ownership is untouched, and those tests pass without any cloud, state or secret access.
由索引模型根据 Issue 内容生成。
描述
Raw intake
During DTC #455 exact-head deployment diagnosis, a read-only source audit found that deploy/deployment_targets.py at fde01ffa3f46e790ec0d05f13f80fd8ddfce6a7c labels the website-development target's terraform_root as main/website (line 533).
Current AWS committed source at 2b9b0102dc19c9925e84862213b7de9f5d19ee4b owns development website resources under main/dev; main/website is the production root. The misleading field also appears in deployment receipts and can confuse recovery root selection.
This is separate from the failed deployment's secret-name-set mismatch. Current DTC and AWS secret-reference declarations agree; the selected live website-dev-web:22 differs. Changing ownership metadata alone does not establish runtime recovery.
Please groom a narrow source metadata correction and its existing contract coverage under the normal independent lifecycle. Preserve target/account/region/secret/image guards, production ownership and all UI/features. No cloud apply, credentials/state/secret-value access, database reset, or deployment retry is authorized by this intake.
Evidence: #455 on-call receipt https://github.com/DataTalksClub/website/issues/455#issuecomment-6085255922 and AWS #58 recovery handoff https://github.com/DataTalksClub/aws-infra/issues/58#issuecomment-6085435261 .
- 主要语言
- Python
- 星标
- 0
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DataTalksClub/website 的其他 Issue
-
bug infra operations P1 testing
难度 2/5 1-3 小时 新手友好度 72/100
DataTalksClub/website#329 ·
-
bug content data-migration documentation events operations P1
难度 2/5 1-3 小时 新手友好度 84/100
DataTalksClub/website#327 ·
-
bug frontend P0 testing
难度 2/5 1-3 小时 新手友好度 90/100
DataTalksClub/website#300 · 7 条评论 ·
-
bug data-migration events P0 testing
难度 2/5 1-3 小时 新手友好度 72/100
DataTalksClub/website#295 · 6 条评论 ·
-
bug needs grooming P1 testing
难度 4/5 3-5 天 新手友好度 35/100
DataTalksClub/website#473 ·
查看 DataTalksClub/website 的全部 Issue
相似的 Issue
-
intake mcp-intake needs-ac needs-human-review priority:medium
难度 2/5 1-3 小时 新手友好度 67/100
Ikalus1988/MisakaNet#3848 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 75/100
521xueweihan/HelloGitHub#4105 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
igormcsouza/bookloud#54 ·
-
难度 1/5 1 小时以内 新手友好度 90/100
aws-samples/sample-per-model-bedrock#526 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
ok-oldking/ok-wuthering-waves#1802 ·
维护者通常 2 天内回复