You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow Airflow CLI's dag subcommands , pause and unpause, to support multiple DAG IDs instead of only one.
Use case/motivation
There are cases where we would like to pause or resume multiple DAGs at once. As a Cloud Composer user - I'd like to do both, for example, before and after upgrading an environment, in correspondence. The current methods of doing it, at least in Cloud Composer, are manually via the UI (not scalable), via Airflow API using dag_id_pattern (not easily accessible, at least in CC), or one-by-one via the CLI - most straightforward to perform, but only supports one DAG id per run (considering the extra overhead for accessing the CC's GKE - it could take up to a minute to pause or unpause each DAG!).
Related issues
Possible Caveats
#32360 - as dag_id_pattern might be changed in Airflow's API - the method for passing multiple DAG ids should be considered.
Or separately. There is no particular reasons to bundle such things together, the smaller the scope of the PR, the higher chance someone will complete it and the faster it goes through review.
shahar1
changed the title
Add CLI support for bulk pause and resume of DAGs
Add CLI support for bulk pause and unpause of DAGs
Mar 18, 2024
shahar1
changed the title
Add CLI support for bulk pause and unpause of DAGs
Add CLI support for bulk pause and resume of DAGs
Mar 18, 2024
Description
Allow Airflow CLI's
dag
subcommands ,pause
andunpause
, to support multiple DAG IDs instead of only one.Use case/motivation
There are cases where we would like to pause or resume multiple DAGs at once. As a Cloud Composer user - I'd like to do both, for example, before and after upgrading an environment, in correspondence. The current methods of doing it, at least in Cloud Composer, are manually via the UI (not scalable), via Airflow API using
dag_id_pattern
(not easily accessible, at least in CC), or one-by-one via the CLI - most straightforward to perform, but only supports one DAG id per run (considering the extra overhead for accessing the CC's GKE - it could take up to a minute to pause or unpause each DAG!).Related issues
Possible Caveats
#32360 - as
dag_id_pattern
might be changed in Airflow's API - the method for passing multiple DAG ids should be considered.Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: