Skip to content

Commit

Permalink
Start triggerer when start composer-dev
Browse files Browse the repository at this point in the history
RELNOTES=FEATURE

Change-Id: Ie741ab428e9de6bdab63336c6622dd26d149c070
GitOrigin-RevId: 60ceabd179fc80325f29f87592c400b13903173e
  • Loading branch information
moiseenkov authored and ahidalgob committed Mar 28, 2024
1 parent 89c54a5 commit da9dbca
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 0 deletions.
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,10 @@ deployed Cloud Composer images for production purposes.
- If you have only one local environment, you can omit the local environment's
name from all `composer-dev` commands, except the `run-airflow-cmd`.

- Once local environment started, the Airflow triggerer is up along with scheduler and webserver.
Please note that Airflow CLI command `airfow triggerer` was released in Airflow 2.2.0 and thus won't work
with older versions.

## Google Cloud documentation page

See [Google Cloud documentation](https://cloud.google.com/composer/docs/composer-2/run-local-airflow-environments)
Expand Down
1 change: 1 addition & 0 deletions composer_local_dev/docker_files/entrypoint.sh
Original file line number Diff line number Diff line change
Expand Up @@ -39,4 +39,5 @@ if ! grep -Fxq "AUTH_ROLE_PUBLIC = 'Admin'" /home/airflow/airflow/webserver_conf
fi

airflow scheduler &
airflow triggerer &
exec airflow webserver

0 comments on commit da9dbca

Please sign in to comment.