Is there any more detailed documentation, or are there any more detailed examples, of using Pulumi with Azure Devops and Github Actions as CI/CD platforms? I've read the documents available under https://www.pulumi.com/docs/guides/continuous-delivery/. But to me they seem lacking in detail and in addressing real-world scenarios, e.g. a release pipeline which accounts for Test, UAT, and Production environments (since each would be a different Pulumi stack). We're at the point in our Pulumi research where I'm reasonably comfortable with how to write a Pulumi program that will define all our resources and that can be used for different environments / stacks. But unless we're super confident with how Pulumi would fit into our use of CI/CD, we won't be able to go forward with adopting Pulumi. So any help on this front? Thank you.

We generally use GitHub Actions on many of our open-source repos at https://github.com/pulumi. As a lot of them do a bit of gymnastics to build because we have to build the actual package, I'm asking around for more straightforward examples internally. For Azure DevOps, here's an example from our examples repo: https://github.com/pulumi/examples/tree/master/classic-azure-ts-appservice-devops

We also adopted Pulumi for all of our projects and are using GitHub Actions as a CI/CD platform. I'm talking about some 30 repositories ranging from simple ones to those needing a little bit more orchestration (e.g. creating Lambda deployment packages, multiarch Docker image builds or interleaving Pulumi provisioning with building applications on the runner). So far we haven't encountered anything that wouldn't be solved and are more than happy.