Given this context:
Deploying Airflow DAGs via the Paved Road Pipeline  
The Paved Road Pipeline uses the container at https://gitlab.com/JohnLewisPartnership/jlp-data-platform/data-engineering/pdp/gcp/cloud-composer/common-container-images/pdp-composer-deployscripts
to deploy DAGs. There's lots of helpful information in that repo's README.NAME_1.
We'll just repeat the salient points, and more info on how
this is used with the Paved Road Pipeline here.  
Defining Airflow DAGs in your Paved Road Pipeline  
The airflow block in your data product definition defines
which DAGs and folders to deploy to the Airflow servers.  
yaml
airflow:
dags:
- file: /path/to/in/your/repo/file.py
targets:
- demo2
- mcmtest
- prod
- folder: /path/to/a/subfolder
targets:
- demo2  
You can either specify a single file, or a folder,
in which case the whole directory will be recursively copied
to the server.  
You must specify which airflow environments you want to deploy to.
We don't deploy to any environments unless you specify them.  
Important! Files will be deployed to a subfolder on the
airflow server which corresponds to your projects shortname  
Targeting a default composer instance  
Every environment (e.g. demo2) has a default composer instance,
for both Composer1 and Composer2. If you don't specify a particular
composer instance in a targets_specific block, your DAG will
go to the default composer instance for the version (default 2) that
you are targeting.  
Targeting a specific composer instance  
You can use a targets_specific block to name an exact composer instance,
in case you don't want the default.  
yaml
airflow:
dags:
- file: file1.py
targets:
- demo2
targets_specific:
- composer-regtest-6  
Note that you can have both targets and targets_specific blocks
for a DAG. In this case the DAG will go to the default demo2
Composer, but the specified regtest one.  
Targeting a demo2 green composer instance (for now only demo2 green is available, regtest & prod green are not available)  
yaml
airflow:
dags:
- file: file1.py
targets_specific:
- pdp-composer-demo2-green  
Targeting Composer v1  
We do support deploying to Composer v1, but unless you specifically
target it, will default to Composer v2. To request a v1 deployment:  
yaml
airflow:
dags:
- file: file1.py
targets: demo2
target_airflow_major_version: 1  
This will cause the DAG to go to the default demo2 instance for
Composer 1.  
Config substitution during DAG deployment  
When we deploy your DAG, we'll automatically substitute
Jinja strings like {{ pipeline_config.base.th Write your response with at least 500 words.
user