Skip to content

Add per-environment DAG branch config#86

Draft
thomasyu888 wants to merge 1 commit into
tyu-test-kube-executorfrom
tyu-dev-read-from-dev-branch
Draft

Add per-environment DAG branch config#86
thomasyu888 wants to merge 1 commit into
tyu-test-kube-executorfrom
tyu-dev-read-from-dev-branch

Conversation

@thomasyu888
Copy link
Copy Markdown
Contributor

@thomasyu888 thomasyu888 commented Apr 14, 2026

Problem:

  • The DAG git-sync branch is hardcoded to main in values.yaml, meaning dev and prod always sync DAGs from the same branch with no way to test DAG changes in isolation

Solution:

  • Added a dags_git_branch variable threaded through the Spacelift stack modules and the Airflow module, overriding dags.gitSync.branch and dags.gitSync.ref via ArgoCD Helm parameters
  • Dev environment syncs DAGs from orca-recipes:develop, prod from orca-recipes:main
  • Staging falls back to the default of main

Testing:

  • Confirm dev Airflow is syncing DAGs from the develop branch of orca-recipes
  • Confirm prod Airflow continues to sync from main

🤖 Generated with Claude Code

@thomasyu888 thomasyu888 changed the base branch from main to tyu-test-kube-executor April 14, 2026 16:00
@thomasyu888 thomasyu888 changed the title Add CeleryKubernetesExecutor and per-environment DAG branch config Add per-environment DAG branch config Apr 14, 2026
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.

1 participant