Miretpl commented on code in PR #65758: URL: https://github.com/apache/airflow/pull/65758#discussion_r3175137599
########## chart/reproducible_build.yaml: ########## @@ -1,2 +1,2 @@ release-notes-hash: d05c9f69d0a418b377ccd2a4328c4bb8 -source-date-epoch: 1776802957 +source-date-epoch: 1777089568 Review Comment: We should not modify it as it is modified during the chart release. ########## chart/docs/manage-dag-files.rst: ########## @@ -108,6 +108,10 @@ This option will always use running Git-Sync sidecar on every dag-processor, wor The Git-Sync sidecar containers will sync Dags from a git repository every configured number of seconds. If you are using the ``KubernetesExecutor``, Git-Sync will run as an init container on your worker pods. +If you want the synced files to appear under a different directory name than ``repo`` inside the DAG mount path, +set ``dags.gitSync.link`` in your ``values.yaml``. For example, ``link: myrepo`` will mount DAGs under +``$AIRFLOW_HOME/dags/myrepo`` instead of ``$AIRFLOW_HOME/dags/repo``. Review Comment: ```suggestion If you want the synced files to appear under a different directory name than ``repo`` inside the Dag mount path, set ``dags.gitSync.link`` in your ``values.yaml``. For example, ``link: myrepo`` will mount Dags under ``$AIRFLOW_HOME/dags/myrepo`` instead of ``$AIRFLOW_HOME/dags/repo``. ``` there was a community decision during Airlfow 3.0 release that we "own" Dag name, so we should use everything `Dag` instead of `DAG` now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
