Skip to content

Could not get DAG access permission after upgrade to 2.3.0 #23473

@leehuwuj

Description

@leehuwuj

Apache Airflow version

2.3.0 (latest released)

What happened

I upgraded my airflow instance from version 2.1.3 to 2.3.0 but got issue that there are no permission for new DAGs.
The issue only happens in DAG which has dag_id contains dot symbol.

What you think should happen instead

There should be 3 new permissions for a DAG.

How to reproduce

  • Create a new DAG with id, lets say: dag.id_1
  • Go to the UI -> Security -> List Role
  • Edit any Role
  • Try to insert permissions of new DAG above to chosen role.
    -> Could not get any permission for created DAG above.
    There are 3 DAG permissions named can_read_DAG:dag, can_edit_DAG:dag, can_delete_DAG:dag
    There should be 3 new permissions: can_read_DAG:dag.id_1, can_edit_DAG:dag.id_1, can_delete_DAG:dag.id_1

Operating System

Kubernetes

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions