Azure-devops-docs: [Approvals] Pipeline variable for environment approval

[aapalm]

Is there a way to fetch the approver's id / email and date in the pipeline? I can't seem to find any predefined variable or REST API for this.

For releases, there was a PreDeployApprovals and PostDeployApprovals we could use.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b067a175-f640-7503-9c1e-f0130c6dbeda
• Version Independent ID: ff743c7b-a103-eae6-4478-62ba995a4b36
• Content: Pipeline deployment approvals - Azure Pipelines
• Content Source: docs/pipelines/process/approvals.md
• Product: devops
• Technology: devops-cicd
• GitHub Login: @shashankbarsin
• Microsoft Alias: shashban

[WilliamAntonRohm]

Thanks for your question. It looks like you're working through an issue with your scenario or implementation, rather than an issue with the documentation. Here are a couple of options where you might consider asking your question:

• Azure DevOps on Stack Overflow
• Azure DevOps Support Bot

I am closing this issue now. You are welcome to @ mention me for any followup or to let me know your results. We hope to hear from you again.

[nicolasproton]

I have the same problem with my YAML pipeline. I am not able to (or don't know how to) retrieve the environment approver(s) for a deployment step. There is no documented API.

[aapalm]

@nicolasproton , @Materia-xx, created a community feature request, feel free to vote for it
https://developercommunity.visualstudio.com/content/idea/925034/multi-stage-pipeline-variable-for-environment-appr.html

[cmitescu]

hello,
we have the same problem and we really need to extract the message the user is specifying in the approval section in order to pass it further down the pipeline.
Can we do something about this or is it something already put in place that we can in a similar way?

Thank you in advavnce,
-Cosmin

[WilliamAntonRohm]

@aapalm, @nicolasproton, @cmitescu -- thank you for clarifying.

@shashankbarsin -- please look into this potential documentation issue.

[manivasm]

any update on this.