Loading
Provision EnableCodeReviewFlowService as the group owner
What does this merge request do and why?
The service ran the Duo settings cascade without a user, so the foundational flow sync rejected the Code Review flow and created no service account, but the setting was still marked enabled.
It now provisions the flow on the top-level group as an active owner, matching how the flow is enabled from the settings page, and only cascades and marks the setting enabled when that succeeds. Otherwise the setting stays pending so the next provisioning run retries.
References
Screenshots or screen recordings
| Before | After |
|---|---|
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.