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

Really need an answer for this. :pray: My current workaround is to create Pulumi.stack-name.yml for the new stack dynamically in the ci and then discard it which is super hacky. Use case is automated branch deployment on pull requests.

Is it essential that you use Pulumi's Config object? Can you get the values using env vars or similar?

<@U012UJTT55M> I could for everything else but the `aws:region` which is required by the @pulumi/aws package and I haven’t found a work around for that

<@UHTP242EB> could you have a look at this please?