Any idea how I can make sure automation actually loads Pulumi.<stackname>.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.
03/28/2021, 5:01 PM
Yes, all references to config must be made from within the inline program. Config is populated via the connection to the pulumi engine during