zach-overflow commented on issue #49651:
URL: https://github.com/apache/airflow/issues/49651#issuecomment-2916321656
Thought I'd chime in with some extra details for similar unexpected behavior
I've observed in Airflow `3.0.1`. @sjyangkevin if you're working on this,
hopefully my notes below might add some helpful context:
I can also second that I see this behavior as OP described, and I'm seeing
the behavior when setting the `access_control` value to a value following the
newer permissions format within my custom dag_policy like so:
```python
def dag_policy(dag: DAG) -> None:
dag.access_control = {
"some-nonexistent-custom-role": {
"DAGs": {"can_edit", "can_read"},
"DAG Runs": {"can_create", "can_read", "can_delete"},
}
}
```
So if I'm not mistaken this issue appears to be reproducible for both the
older `access_control` format, and the newer format.
--
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]
