Mark duoWorkflowWorkflows GraphQL query as generally available

Sebastian Rehmrequested to merge
duo/update/607860-graphql-duo-workflow-workflows-ga into master

What does this MR do and why?

Makes the Query.duoWorkflowWorkflows GraphQL field generally available. This is a follow-up to !258242 (merged), which makes the Trigger a flow REST endpoint GA. Without this change, customers could start a flow through a GA API but could only read its result through an experimental one.

Changes:

  • Remove experiment: { milestone: '17.2' } from duo_workflow_workflows in ee/app/graphql/ee/types/query_type.rb.
  • Regenerate the GraphQL reference docs. This removes the Status: Experiment details block.
  • Regenerate the introspection schemas. The field is no longer marked deprecated, and it now appears in introspection_result_no_deprecated.json.

What stays experimental

  • Project.duoWorkflowWorkflows uses the same resolver and was already not marked as an experiment, so it doesn't change.
  • Fields and arguments on DuoWorkflow that have their own experiment: marker (for example firstCheckpoint/latestCheckpoint checkpointNs) stay experimental. Only fields and arguments without a marker become part of the GA contract.

What GA means for this field

After this merges, the field is covered by the GraphQL deprecation policy. An earlier review found no breaking schema changes to this field in the last four months. It did find two behavior changes that clients could notice: single-flow lookup errors are now merged into WORKFLOW_NOT_FOUND, and flows started from Slack are now private to the user who started them. See !258242 (comment 3929122982).

References

Screenshots or screen recordings

Not applicable. There are no UI changes.

How to set up and validate locally

  1. bundle exec rake gitlab:graphql:check_docs
  2. bundle exec rake gitlab:graphql:generate_all_introspection_schemas and confirm there is no diff.
  3. In GraphiQL, confirm that duoWorkflowWorkflows on Query no longer shows as deprecated or experimental.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports