Skip to content

fix(rds-postgres-server): propagate TFSTATE_BUCKET through link/unlink workflows#12

Merged
sebastiancorrea81 merged 1 commit intomainfrom
fix/rds-postgres-server-tfstate-bucket-link
Apr 21, 2026
Merged

fix(rds-postgres-server): propagate TFSTATE_BUCKET through link/unlink workflows#12
sebastiancorrea81 merged 1 commit intomainfrom
fix/rds-postgres-server-tfstate-bucket-link

Conversation

@sebastiancorrea81
Copy link
Copy Markdown
Contributor

Summary

  • build_permissions_context leía tfstate_bucket de values.yaml, pero esa key nunca estuvo definida ahí, dejando el bucket vacío en el terraform init de link/unlink
  • Se agrega TFSTATE_BUCKET al output del step build_context en link.yaml y unlink.yaml, alineándose con el patrón de rds-postgres-db
  • Se reemplaza la lectura vía yaml_value por consumo directo de la variable de entorno, con un guard explícito que falla rápido si no está seteada

Why it didn't fail before

build_permissions_context solo corre en workflows de link y unlink — nunca en create, update o delete. Instalaciones que nunca hicieron un link no se vieron afectadas.

Test plan

  • Crear un servicio rds-postgres-server
  • Ejecutar un workflow de link y verificar que TFSTATE_BUCKET llega correctamente a build_permissions_context
  • Verificar que terraform init usa el bucket correcto (np-service-<SERVICE_ID>)
  • Ejecutar unlink y verificar el mismo comportamiento

🤖 Generated with Claude Code

…k workflows

build_permissions_context was reading tfstate_bucket from values.yaml (which
never defined it), causing an empty bucket name on terraform init during link
and unlink actions. Align with rds-postgres-db pattern: export TFSTATE_BUCKET
from build_context via workflow output and consume it from the environment.
Added an explicit guard in build_permissions_context to fail fast if the var
is missing.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@sebastiancorrea81 sebastiancorrea81 merged commit b3d2f22 into main Apr 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants