Loading
ff: Split the suspendable DAP runner tag into its own feature flag
<
What does this MR do and why?
Splits suspendable_environment_for_dap in two so the suspend-capable runner fleet can roll out independently of resumability.
suspendable_workload_tag_for_dap(new,wip): routes DAP workloads togitlab--duo--suspendableinstead ofgitlab--duo. DrivesWorkflow.workload_tag_for, so runner readiness checks and "no eligible runner" messages follow it too.suspendable_environment_for_dap: now only setssuspend_on_success,suspend_on_failureandruntime_environment_key.
Rollout issue: #630540
Before this deploys: suspendable_environment_for_dap is enabled on gprd for gitlab-org/duo-workflow/test-project-playground/aherczeg. Enable suspendable_workload_tag_for_dap for the same project first, or its workloads fall back to gitlab--duo.
How to set up and validate locally
- Register a GDK runner tagged
gitlab--duo--suspendableand one taggedgitlab--duo. - In the Rails console:
Feature.enable(:suspendable_workload_tag_for_dap, project)andFeature.disable(:suspendable_environment_for_dap). - Start a remote flow in that project. The
gitlab--duo--suspendablerunner picks up the workload job, and its log prints no runtime environment key at completion. - Flip both flags the other way and start another flow. The
gitlab--duorunner picks up the job, and it is suspended at completion (the log prints a runtime environment key).
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist.
</