Trigger button should be greyed out when no permissions to trigger DAG

[BasPH]

Apache Airflow version

Other Airflow 2/3 version (please specify below)

If "Other Airflow 2/3 version" selected, which one?

3.1.0

What happened?

My user has no permission to trigger DAGs (i.e. no permission to create DAG runs).

However, in the UI, the trigger DAG button is accessible:

You can enter details, and only after clicking the "Trigger" button do you receive an error:

It would be more intuitive to grey out the button when the user has no permissions to trigger DAGs.

What you think should happen instead?

No response

How to reproduce

Run Airflow with read-only permissions

Operating System

Linux

Versions of Apache Airflow Providers

No response

Deployment

Astronomer

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

[tirkarthi]

There is an endpoint to return menus allowed with the UI disabling them menus not accessible in the UI. Perhaps there could be new API to dump the permissions relevant to UI like create a dagrun to disable/enable trigger button, delete a dagrun to enable/disable delete dagrun button etc.

https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/api_fastapi/core_api/routes/ui/auth.py

airflow/airflow-core/src/airflow/ui/src/layouts/Nav/Nav.tsx

Lines 163 to 168 in efa1084

	<NavButton
	disabled={!authLinks?.authorized_menu_items.includes("Dags")}
	icon={DagIcon}
	title={translate("nav.dags")}
	to="dags"
	/>

[bbovenzi]

@vincbeck maybe its time to build a full permissions endpoint?

[potiuk]

FYI @vincbeck has holidays and no computer with him. (🌴 )