FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Consolidating Broker deployment into one workflow
Running build, candidate, canary, and traffic switching serially in the same run
Purpose
Passing Broker build, preparation, release, and traffic state across separate workflows and artifacts made inputs and state difficult to follow. A single manual entry point needed to execute the safety gates in order within one run.
Implementation
Four former workflows were consolidated into broker deployment workflow, with serial steps for source checks, shared-contract and Broker builds, immutable image creation, candidate planning and application, the canary, and traffic planning and application.
Identity separation for build, Terraform plan, and Terraform apply, along with fixed-target checks, was preserved. A failed canary stops without changing traffic, while run-ID input, separate dispatches, and cross-workflow artifact handoff were removed.
Rendering diagram…
What was confirmed
Verification results
YAML parsing, GCP static verification, specification auditing, Terraform formatting, repository-wide verification, and the diff check passed.
Static checks confirmed that the four former workflows were removed and only the new single workflow retained the Broker deployment sequence.
Executing this workflow and switching traffic had not been verified by the cutoff.
Basis for completion
This scope ended when one manual workflow statically preserved serial gates, no traffic change after canary failure, and identity separation.