Draft: Expose the trigger service account role in GraphQL

Eduardo Bonetrequested to merge
594180-autonomous-trigger-sa-graphql into 594180-autonomous-trigger-sa-role

Stack

  1. !251852 — column and model
  2. !253659 — provisioning at the default role
  3. !253667 — choosing the role, and the ceiling
  4. This MR — serviceAccountAccessLevel GraphQL argument

What does this MR do and why?

Adds serviceAccountAccessLevel to aiFlowTriggerCreate and aiFlowTriggerUpdate, so the trigger form can pick the project role for an autonomous trigger's dedicated service account.

The service layer already accepts the parameter and caps it, so this only opens the API. The value is ignored for triggers without an autonomous event type.

Related: #594180

Testing

Mutation argument specs cover the new argument on both mutations. The behaviour it drives is covered in !253667.

Edited by Eduardo Bonet

Merge request reports