I've recently tried converting our UI or Classic based Release pipeline over to a YAML based release pipeline.
We have three environments, initially a CD build will happily deploy to our Development environment.
From there we manually trigger a release (re: promotion) to Test, and then at some point, if we're all happy, manually promote to Production.
We know we can't mimic the manual promotion between releases stages as it's not currently supported, but from what I've read, we should be able to do the same thing by defining a security check for each environment where the manual promotion was requested.
The details for defining security checks are here: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/approvals?view=azure-devops&tabs=check-pass
I've since added that same security check to both Test and Production, but the releases still happen automatically.
Is there a sample of where this kind of approval process is mapped into the new YAML multi-stage releases?
So far I've added a security group to the Test and Production environment, via the Approval and checks feature on the Environments tab.
