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.

Pulumi Community

Hello Pulumi-ers. I have been learning more devops IaC. AWSCDK, CDKTF, and Pulumi! Let me tell you, I love Pulumi the most by far! The handlebars are welcomed! You all rock!

I have a question about deployments strategies...
I have explored 3 deployment strategies using AWS and GitHub:
• (good) GitHub Actions, via your own docs, storing my AWS roles (dev, staging, prod) as ENV vars in github itself.
• (better) Github Actions like this ^^^, except env vars are stored on pulumi ESC per ENV.
• (best?) Forget github actions, just use Pulumi Deployments to watch my repos push/PR changes. Pulumi handles "actions", deployment, stacks, & secrets. Github only needs to worry about code itself. 
Am I correct in understanding that the Pulumi "Deployments" are easiest to use but the least configurable/customizable? For example, I am using `pnpm` in my monorepo and Delployments use `npm`. What if I wanted to add some other jobs? For example, testing, Docker building/uploading.  Pulumi would not support something like this correct? Is it correct to say... "Pulumi Deployments are a great way to get your environments deployed quickly, but if you need more control you should look to using GitHub Actions" Thanks!