choo121600 commented on code in PR #53176: URL: https://github.com/apache/airflow/pull/53176#discussion_r2316353575
########## airflow-core/docs/authoring-and-scheduling/ownership.rst: ########## @@ -0,0 +1,36 @@ + .. 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. + + +.. _ownership: + +Ownership +========= + +When multiple users are authoring the DAGs of a single Airflow instance, it can be tedious to know who is responsible of what. Review Comment: we've decided to refer to “DAG” as “Dag” from now on, so please change it accordingly. ########## airflow-core/docs/authoring-and-scheduling/ownership.rst: ########## @@ -0,0 +1,36 @@ + .. 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. + + +.. _ownership: + +Ownership +========= + +When multiple users are authoring the DAGs of a single Airflow instance, it can be tedious to know who is responsible of what. +One way to overcome this is to attach owners, allowing users to know who is in charge of a particular DAG or Task. + +This ownership is split in two parts: + +1. at the Task level, through the ``owner`` argument of the :class:`~airflow.models.baseoperator.BaseOperator`; +2. at the DAG level, to customize the UI through the ``owner_links`` definition. + +In Airflow 2, the list of owners was displayed in the DAG list view, not taking into account the ``owner_links`` value. Review Comment: This is misleading because it generalizes for all of Airflow 2. The `owner_links` feature was added in version 2.4.0, so it did work in later Airflow 2 releases. https://airflow.apache.org/docs/apache-airflow/2.4.0/howto/add-owner-links.html -- 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]
