Blocking modify workflow when not notes
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### Description
Our Airflow operators require the following functionality:
A valid note (i.e., a non-empty string) must be entered whenever any modification action related to a task instance or DAG run is performed.
If the note is missing, an error should be displayed. For example:
_You are not allowed to modify the current dag run without entering a reason in the notes._
This feature should be disabled by default and configurable in airflow configuration file.
This feature is needed because several operators operate one airflow instance and admins want to know the reason of all modification including its history in audit log.
### Use case/motivation
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
Contributor guide
Research direction
No files, tests, configuration key, or entry points are named. First identify every task-instance and DAG-run modification path, the configuration mechanism, and the audit-log behavior; done should include a defined scope, a disabled-by-default setting, validation for non-empty notes, and tests for the resulting error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100