Loading
Exposes duo_scheduled_triggers_enabled in the project REST API
What does this MR do and why?
Part of #634139 and MR 6 of 6.
Exposes duo_scheduled_triggers_enabled in the project REST API, renames the feature to "scheduled automations" in the docs, and documents the project-level setting that !265546 (merged) adds.
The automations rename only focuses on the user facing objects and leaves the internal implementations (i.e. API, service names, audit events, etc.) alone as triggers
- Add duo_scheduled_triggers_enabled cascading se... (!264600 - merged)
- Enforce the scheduled triggers setting (!265174 - merged)
- Add the scheduled automations setting to the Du... (!265569 - merged)
- Show when scheduled runs are turned off and blo... (!265545 - merged)
- Add scheduled automations setting to Projects (!266298 - merged)
- This MR
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
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.
Edited by Shola Quadri