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

Enforce unique CloudFormation stack names

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

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
aws, typescript
Ambito
devops

Direzione di ricerca

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.

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

Descrizione

bug good first issue medium priority t-infra

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-buckets
  • apify-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.

Lingua principale
TypeScript
Stelle
15
Fork
7
Merge medio
1g 16h
PR unite (30g)
5

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 apify/workflows

Tutte le issue di apify/workflows

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.