josh-fell opened a new pull request #19400:
URL: https://github.com/apache/airflow/pull/19400


   There is an ongoing effort to enhance example DAGs by setting static values 
for `start_date`, ensuring `catchup=False` is set, cleaning up and/or 
implementing useful `default_args`, and removing/limiting the use of redundant, 
default connection ID values.
   
   This PR mainly addresses the static `start_date` and `catchup` clean up 
areas in example DAGs in the across non-Google Cloud providers (e.g. Ads, 
Firebase, LevelDB, Marketing Platform, and Suite). 
   
   The following additional (small) updates are also included:
   -  The `example_campaign_manager` example DAG was updated to take advantage 
of `XComArgs` rather than the classic Jinja templating to pull `XComs`.
   - Updated task-dependency notation in `example_firestore` to improve 
readability using `chain()`.
   - Removed unnecessary setting of `dag=dag` in `example_leveldb`
   
   > Note: There was an opportunity to consolidate task args to `default_args` 
for most, if not all, DAGs. However, these updates were not implemented as they 
would have conflicted too much with the operator documentation that references 
the example DAGs.
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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]


Reply via email to