This message was deleted.

sparse-intern-71089

05/16/2022, 4:30 PM

This message was deleted.

clever-sunset-76585

05/16/2022, 6:32 PM

The task extension doesn't currently automatically capture stack outputs and make them available to subsequent steps. So yeah you'd have to add a separate step to do that yourself by running

pulumi stack output

and setting it as an output variable using https://docs.microsoft.com/en-us/azure/devops/pipelines/process/set-variables-scripts?view=azure-devops&tabs=bash

clever-sunset-76585

05/16/2022, 6:32 PM

There is also https://github.com/pulumi/pulumi-az-pipelines-task/issues/60

👍 1

rough-window-15889

05/16/2022, 6:41 PM

I really specifically want to output the diff results from the preview rather than the stack outputs but that all makes sense. Thanks!

clever-sunset-76585

05/16/2022, 6:43 PM

Gotcha i see what you mean now by "preview output"...yeah you'd have to manually get the diff result. There is an issue for that as well in that repo, if you want to comment about your use case there and +1 it.

❤️ 1

rough-window-15889

05/16/2022, 6:45 PM

Will do

clever-sunset-76585

05/16/2022, 6:45 PM

https://github.com/pulumi/pulumi-az-pipelines-task/issues/87 talks about something similar.

110 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.