Draft: docs: document duo_remote_flows_enabled API

Relates to issue #585775

Changes

This MR adds comprehensive documentation for managing GitLab Duo remote flows via the API.

doc/api/groups.md

  • Added duo_remote_flows_availability attribute to the Update group attributes table with description explaining it's a convenience attribute for Premium and Ultimate tiers
  • Added explanatory note after the attributes table clarifying the relationship between duo_remote_flows_availability, duo_remote_flows_enabled, and lock_duo_remote_flows_enabled
  • Added three example API requests demonstrating:
    1. Getting group settings including duo_remote_flows_availability
    2. Enabling GitLab Duo remote flows using duo_remote_flows_availability=true
    3. Disabling GitLab Duo remote flows using duo_remote_flows_availability=false

doc/api/settings.md

The settings.md file already contains complete documentation:

  • duo_remote_flows_enabled and duo_remote_flows_availability documented in the Available settings table
  • lock_duo_remote_flows_enabled also documented
  • Comprehensive note explaining the relationship between these attributes
  • Complete example API requests showing how to get and set these values

Key Documentation Points

  1. Two Approaches: Users can manage GitLab Duo remote flows using either:

    • The convenience attribute duo_remote_flows_availability (simpler, manages both enable and lock settings)
    • Direct control with duo_remote_flows_enabled and lock_duo_remote_flows_enabled (granular control)
  2. Behavior:

    • Setting duo_remote_flows_availability=true enables remote flows and unlocks the setting
    • Setting duo_remote_flows_availability=false disables remote flows and locks the setting
  3. Availability: These features are available for Premium and Ultimate tiers only

Edited by Duo Developer

Merge request reports

Loading
Loading