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

Any idea how I can make sure automation actually loads Pulumi.&lt;stackname&gt;.yaml from disk? Or is the intention of automation to get rid of it? I really thought it had succeded as it didn't prompt me for passphrase for secrets + my secretsprovider is configured on each stack.. but it seems like it's completely ignoring the config otherwise in the running of the program.
Edit: stack.getConfig() got me the confirmation I needed. Issue was that the modules for each type of infra I was provisioning had the pulumi.config() and config.requireObject() stuff outside of the exported function. Sigh.

Yes, all references to config must be made from within the inline program. Config is populated via the connection to the pulumi engine during `up` and `preview`  before the inline program is invoked.