Set Azure Pipeline task status to warning when warning(s) exist from Pulumi Policy-as-Code #146
Labels
customer/feedback
Feedback from customers
impact/usability
Something that impacts users' ability to use the product easily and intuitively
kind/enhancement
Improvements or new features
Currently, when policy violation warnings exist on a stack, the status for the Azure pipeline task is green. Teams need to parse the logs to determine whether any warnings exist. This can be problematic if a new policy is rolled out, and teams forget to review the logs if no infrastructure changes were made. By leveraging the Azure task status options, teams can easily identify when such warnings exist.
Alternatively, we would need to create a powershell task, leverage the Pulumi REST api to pull the stack details, determine if any warnings exist, and set the appropriate task status where appropriate.
The text was updated successfully, but these errors were encountered: