Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Correct development target Terraform owner metadata

Aperta
  • Qualcosa non va?
#459 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
50/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
devops, infrastructure

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug infra needs grooming

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 .

Lingua principale
Python
Stelle
0
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DataTalksClub/website

Tutte le issue di DataTalksClub/website

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.