-
Notifications
You must be signed in to change notification settings - Fork 15.8k
Open
Labels
area:corekind:bugThis is a clearly a bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet
Description
Apache Airflow version
3.1.0
If "Other Airflow 2 version" selected, which one?
No response
What happened?
Upgraded from Airflow 3.0.7 to Airflow 3.1.0 and the negation has to be before the exclusion for my DAG to appear in the UI.
Behaviour before:
*.py
!dag_to_appear.py
Behaviour after:
!dag_to_appear.py
*.py
If I understand correctly in the docs negations should come after the generic exclusion.
What you think should happen instead?
No response
How to reproduce
Write the negation after exclusion pattern.
Operating System
MacOS with Podman Desktop
Versions of Apache Airflow Providers
No response
Deployment
Docker-Compose
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
area:corekind:bugThis is a clearly a bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet