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

I created a ProviderHelper so I can switched between aws accounts with using statements.
<https://gist.github.com/dbeattie71/2f5824aa9884b233ad10f098eb3b49a5>

And some reflection to get access to _transformations.  That might not be needed with automation-api now.

So it definitely looks like the provider config can be bypassed / overridden via provider args, which avoids the provider static config issue.

I'm still wondering if Pulumi config matters... if I inject an `IOptions&lt;T&gt;` config into a stack instance I don't need to roundtrip config through the Pulumi config api, unless I'm missing something.

Presumably Pulumi up runs without any config if config already manifests in stack resource declarations - by being passed to the ctor and used from there.

I'll try to put an example repo on GitHub that I can point to rather than waving my hands

image.png

Not using all those config options, trying several things out.

Yep, I'm doing something similar. I'm just unsure about using Pulumi config when dotnet config sources are so powerful and I want to just use them.

The helper I created relies on Stack, I'm wondering if there is a way to accomplish the same, with only using a LocalWorkspace and an InlineProgram.

<@UCFNE2370> This might be an example of the config question you were asking, <https://github.com/UbiquitousAS/autodevops/blob/94febfa61fcb4c9156e9198be5149ac16a6b5a8e/Ubiquitous.AutoDevOps/Extensions.cs>