Configure Spinnaker pipeline templates with Managed Pipeline Templates v2 (MPT) to standardize deploy pipelines across microservices with per-service variable overrides

Verified steps

1. Create a pipeline template JSON file defining schema: v2 and a variables block that declares typed parameters such as serviceImage, targetCluster, and rollbackEnabled with default values and description fields
2. In the template stages array, reference variables using ${ templateVariables.serviceImage } in the Docker image field of the Deploy Manifest stage so the template is generic and parameterized
3. Save the template to Spinnaker using the spin CLI command spin pipeline-templates save --file template.json; the template is stored in Spinnaker's front50 service
4. Create per-service pipeline configurations that reference the template using schema: v2 and inherit: pipelineTemplateId; override only the variables block with service-specific values, keeping the stage definitions in the template
5. Use a Spinnaker webhook trigger on each service pipeline and pass trigger.payload fields through to template variables using ${ trigger.payload.imageTag } to enable event-driven deploys from a CI system
6. Configure a canary analysis stage in the template that conditionally enables based on the templateVariables.canaryEnabled variable, using a conditional expression to skip the stage when the variable is false