DEV Community

Discussion on: The NEW Manual Validation Task for Azure DevOps YAML Pipelines Demystified

Collapse
seangwright profile image
Sean G. Wright

Where do you see this manual validation being used when compared to required approvals for environments?

I have yml pipelines setup to move an app through multiple environments of App Services via deployment stages. Each stage after the 'development' environment requires an approval for the DevOps 'Environment' and these approvals can be scoped to specific DevOps users or roles.

The manual validation task is much simpler... 🤔 I'm not sure if I'd use it?

Collapse
n3wt0n profile image
Davide 'CoderDave' Benvegnù Author

Hey, thanks for the question. In YAML the approvals are pre-deployment, this could be used as a workaround to have post-deployment approvals for example. You deploy, and then you pause the stage with a manual validation task so someone can verify that it works, for example.

Or can be something completely unrelated to deployment. Let’s say you are building an application and as part of the process you have to perform a manual action to a 3rd party system that doesn’t have an API you can use for integration…

This task is designed for all the cases like this in which you don’t want or can’t have an automation taking care of “something”.

And I agree with you, it is much simpler than the deployment approvals, at least in its current form, but at least we have something now 😁

Collapse
seangwright profile image
Sean G. Wright

I like your example of post-deployment approvals. I had thought about something like this but didn't know how to implement them. I have been using the Environment approval of each stage as a kind of post-deployment approval of the previous stage.

Lots to brainstorm about here 🤔.

Thanks!