feat: obtain Composer DAGs bucket dynamically #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
DAGS_BUCKETenvironment variable from the deploy workflowgcloud composer environments describeWhy
When Cloud Composer is recreated (for any reason), GCP generates a new bucket with a different hash (e.g.,
gs://us-central1-destaquesgovbr--30208ee3-bucket→gs://us-central1-destaquesgovbr--a02910d4-bucket). This previously broke the deploy workflow until the hardcoded value was manually updated.Benefits
Test plan
workflow_dispatch)🤖 Generated with Claude Code