Allow Deployment Scenario Step Presets
Our deployment targets encompass 100+ tenants, so our deployment process encompasses multiple products within a consistently versioned suite of products.
When we upgrade a client, they receive all components within our suite. However, some of our products support the ability for styling customizations that we like to flow through our standard/normalized release process -- these customizations get versioned in a distinct nuget package and can be redeployed within a release version. This means that our product version is redeployed multiple times for a given client if a new customization is created for a client.
So our deployment process for this suite of products is generalized into templates, but it's a series of steps for granularity to allow for a series of deployment contexts/scenarios by the deployment team.
My proposal would be to allow for deployment process steps to be grouped together into tagged scenarios. These tagged scenarios could be selected at the time of deployment and turn off/on the steps tagged within them. This would allow a subset of a deployment process to be qualified and categorized into a set of scenarios.