Describe Duo Workflow Without Executor architecture
What does this MR do and why?
View rendered markdown at https://gitlab.com/gitlab-org/gitlab/-/blob/explain-duo-workflow-without-executor/doc/architecture/blueprints/duo_workflow/index.md#running-without-the-executor
This came up in recently in Slack (internal).
We want to document this discussion and we can consider this extension of the architecture in future even if we don't implement the required functionality initially. In order to support this we just need to keep the documented constraints in mind.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.