stephen-bracken opened a new issue, #68748:
URL: https://github.com/apache/airflow/issues/68748
### Under which category would you file this issue?
Airflow Core
### Apache Airflow version
3.2.1
### What happened and how to reproduce it?
I have a git repository that is structured like the following:
```
dags/
- path_a/
- example/
- mydag.py
...
- path_b/
- example/
- mydag.py
...
```
I have a dag bundle config like the following:
```
{
"name": "bundle_a",
"classpath": "airflow.providers.git.bundles.git.GitDagBundle",
"team_name": "MyTeam",
"kwargs":
{
"repo_url":"<Dag repository>",
"subdir": "dags/path_a",
"tracking_ref": "dev"
}
},
{
"name": "bundle_b",
"classpath": "airflow.providers.git.bundles.git.GitDagBundle",
"team_name": "MyTeam",
"kwargs":
{
"repo_url":"<Dag repository>",
"subdir": "dags/path_b",
"tracking_ref": "dev"
}
},
```
On the 'Dag Import Errors' popout window in the UI I recieve two dag bundle
errors like the following:
```
Bundle name: bundle_a path: example/mydag.py
Bundle name: bundle_b path: example/mydag.py
```
The import errors are correct, however when I expand the error from
`bundle_a`, the UI also expands the error from `bundle_b` because the dag has
the same path in both bundles.
### What you think should happen instead?
The UI needs to be able to distinguish between two dag import errors that
have the _same dag file path_, but have come from _different dag bundles_. This
is important for multi team deployments where git repos may be split into
different dag bundles, and there may be common dag configuration in multiple
dag bundles.
### Operating System
Debian GNU/Linux 12 (bookworm)
### Deployment
Other
### Apache Airflow Provider(s)
git
### Versions of Apache Airflow Providers
apache-airflow-providers-git==0.3.1
### Official Helm Chart version
Not Applicable
### Kubernetes Version
1.33.5
### Helm Chart configuration
_No response_
### Docker Image customizations
Some additional pip / ubuntu packages installed
### Anything else?
Running on a multi team kubernetes deployment using the apache-airflow
docker image with some customisations.
### Are you willing to submit 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)
--
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]
