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

Hi guys, sorry is this was asked before :pray:
At work we have stacks files, each of them handles cluster provisioning and k8s resources as well as some grafana dashboards.
We have approximately 150 stacks.
I would like to build on top of `pulumi automation api` a way to `make changes to the files and later CI to run refresh a previews in the MR`, but all the examples I saw for `pulumi automation api` interacts directly with the backend (our backend lives in a bucket BTW!) is there any examples or doc to avoid using the state backend and only verify and makes stack files changes?
Thanks!