Skip to main content

Airflow for group members

Signing in​

The Airflow UI is at https://airflow.<base domain>. Sign in with the same Keycloak account you use for Nova — no separate Airflow password. stardelt-admins is synced to Airflow's Admin at every sign-in; everyone else is stardelt-member.

What you see​

The DAGs you see are those of your groups. A member of mobility-analytics sees stardelt__mobility-medallion (and the group's other pipelines). A person in no use-case group sees an empty list; administrators see everything. The DAG id is stardelt__<pipeline name>.

Why a DAG is missing​

A DAG may be missing for one of these reasons:

  • The pipeline has no ownerGroup (administrators only).
  • You are not in the owning group.
  • The DAG was published less than about 25 seconds ago.
  • The group role does not exist yet (the sync Job runs every five minutes).

If it is still missing, ask an administrator to check stardelt-group-<group> in airflow roles list.

Nova or Airflow​

Nova is the front door — scheduling, Run/Pause, the pipeline's definition and its runs. Airflow is for the graph, the Gantt view and the raw task logs. The Run/Pause buttons in Nova work through Nova's service identity; a group member does not need a separate Airflow password for them.

What you may do​

Read and edit (pause, trigger) your group's DAGs and read/create their runs. No delete — deleting a pipeline is a Nova action on the Pipeline resource. Leaving the group takes effect at your next sign-in.

Notebooks and Spark​

A notebook that calls stardelt.spark() needs the pipeline principal's token to carry the lakekeeper audience (the ServicePrincipal default is [trino, lakekeeper]; see the reference and Service principals).