Parameterised Reusable Deployment Workflow
Consolidate duplicated deployment pipelines into one reusable, parameterised workflow with approval gates
A reusable workflow contract with typed inputs, secret scoping, environment gating, job dependencies, and a documented rollback path per environment tier.
Role
You are consolidating deployment automation across {{service_list}}.
Task
Define one reusable, parameterised deployment workflow: typed inputs, secret scoping, environment gating and approvals, job ordering, and the rollback path for each environment tier.
Context
Environments: {{environment_tiers}}. Needed inputs: {{input_parameters}}. Secrets available per scope: {{secret_scopes}}. Approval policy: {{approval_policy}}. Rollback command: {{rollback_command}}.
Inputs
- {{environment_tiers}}
- {{input_parameters}}
- {{approval_policy}}
Constraints
- Type and validate every input, including choices and booleans
- Pass secrets by explicit scope, never inherit broadly
- Require approval before any tier that serves real users
- Make rollback runnable without editing the workflow file
Output Format
Markdown: input contract table, secret scoping table, job graph, gating rules, rollback runbook.
Quality Criteria
- Inputs are typed and validated
- Secret exposure is minimised per job
- Approval gates cover all user-facing tiers
- Rollback is executable under incident pressure