nyoungstudios opened a new pull request, #39772:
URL: https://github.com/apache/airflow/pull/39772

   ## Description
   
   This pull request makes this example DAG work. This DAG uses the XComArg (in 
other words, `.output`) from the first task as the input for the 
`trigger_dag_id` argument in the `TriggerDagRunOperator`.
   
   ```python
   # example dag
   from airflow.models import DAG
   from airflow.operators.python import PythonOperator
   from airflow.operators.trigger_dagrun import TriggerDagRunOperator
   
   with DAG(
       dag_id="trigger_dag",
       description="Tests triggering a dag",
       schedule_interval=None,
       catchup=False,
   ) as dag:
       
       get_dag_id = PythonOperator(
           task_id="get_dag_id",
           python_callable=lambda: "other_dag",
       )
   
       trigger_dag = TriggerDagRunOperator(
           task_id="trigger_other_dag",
           trigger_dag_id=get_dag_id.output,
       )
       
       get_dag_id >> trigger_dag
   ```
   
   ## Open Questions
   
   I left the `or` statement in the `get_link` function of the 
`TriggerDagRunLink` so that past operator links would still work (ones that 
were run before this change). However, if you click the operator link too fast, 
before the `self.trigger_dag_id` is pushed to the XCom, it will use the second 
value in the `or` statement - which will result in an error message.
   
   Here is the code piece I'm referencing:
   
https://github.com/nyoungstudios/airflow/blob/0f6499a8ab04617c29d88a2f435197c199fec72d/airflow/operators/trigger_dagrun.py#L79
   
   This is the error message if you click too fast.
   ![Screenshot from 2024-05-22 
17-20-28](https://github.com/apache/airflow/assets/16254116/e0d2ffcf-6853-44f4-8aa1-578a85b07d52)
   
   ## Testing
   Tested with both Postgres and SQLite databases.
   
   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+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 a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


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