potiuk opened a new pull request #22025: URL: https://github.com/apache/airflow/pull/22025
Many of our users do not understand how DAG deactivation, deletion works - it's quite straightforward for us, who understand how scheduler, serialization and refresh works, but we have not really documented everywhere what the differences are between pausing, deactivation and actual deletion of the metadata. It has been distributed in a few places (API documentation, comments when you issued a "delete" UI action, but I found that there is no single place where it is described. This PR adds documentation in "DAG" page about it - explaining what happens in those different states and instructing the user to follow -> remove dag file -> wait for deactivation -> delete pattern if they want to remove a DAG. Related: #21864 <!-- 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 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/ --> --- **^ 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]
