Skip to content

Freeze OUTBOUND job token scopes in GraphQL API behind FF

What does this MR do and why?

OUTBOUND job token scopes are being retired in favor of INBOUND scopes. OUTBOUND scopes are scheduled for full removal in 17.0, but in the meantime they are being frozen so that they can no longer be expanded. More precisely:

  • New projects can no longer be added to an existing OUTBOUND scope.
  • OUTBOUND scoping can only be disabled. It can not be enabled.

In this change, we disable the legacy behavior on the backend using a feature flag frozen_outbound_job_token_scopes. This flag will be disabled until the frontend has been updated accordingly.

See #395708 (closed)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Hordur Freyr Yngvason

Merge request reports

Loading