Is it possible to access values from `pulumi Config ` inside

Question

Is it possible to access values from `pulumi Config ` inside a Dynamic Provider implementation I ve tried this in both Python and TypeScript and whenever I try to get something from the config I get this error ```error Program run without the Pulumi engine available re run using the `pulumi` CLI```

billowy-army-68599 · Answer

i don t think it s possible at the moment you d need to set a property on the provider and then use `pulumi Config` in your main program and pass it in from there

full-artist-27215 · Answer

ah I see thanks

full-artist-27215 · Answer

Is this documented somewhere and I missed it

billowy-army-68599 · Answer

i ll try dig up the issue but it s there somewhere

billowy-army-68599 · Answer

in general it s best not to have config in providers or components like this anyway

full-artist-27215 · Answer

how so

billowy-army-68599 · Answer

providers and components are intended to be reused if you re adding config you re making that less possible

billowy-army-68599 · Answer

example ```export interface MyAppArgs configItem string export interface MyApp do some stuff here const foo= args configItem ``` if you follow this pattern you can let the user decided if they want to set the config

billowy-army-68599 · Answer

if not you re forcing the user to use config

red-match-15116 · Answer

Amongst probably other reasons your component should have explicit dependencies defined as part of their inputs having a dependency on config is hidden away in the implementation and reliant on global state The reason that this doesn t work though is probably because dynamic providers are serialized into state and config is not available at the time of serialization Also even if it were you would only have the config value at the time of serialization stored in state

billowy-army-68599 · Answer

Komal with the much better explanation than i could hope to give smile

full-artist-27215 · Answer

Gotcha thanks for the explanation

full-artist-27215 · Answer

Sorry to revive a thread but I must have a bad mental model of the under the hood differences between dynamic providers and normal providers I don t have to specify say my `aws region` on every AWS resource I want to create What s the distinction that I m missing

full-artist-27215 · Answer

Thanks in advance bow

red-match-15116 · Answer

For aws I believe the region is a property set on the default provider

red-match-15116 · Answer

So the provider object being passed around to each resource contains the region It all just happens sort of magically when you don t use an explicit provider object

full-artist-27215 · Answer

Right but I still don t need to set the region as an input to any specific resource Is it different with a dynamic provider because the provider is or at least seems to be bundled up with the resource itself

red-match-15116 · Answer

gt Right but I still don t need to set the region as an input to any specific resource But you do need to set it as an input to the provider which itself is an input to each resource

full-artist-27215 · Answer

So my particular dynamic resource needs to access the configuration information from another provider to be concrete I need to work around a hole in the Vault provider to create a particular resource in Vault so I want to use the same Vault connection parameters that the rest of my project is using However it doesn t even appear that I can call say `pulumi Config require vault address ` anywhere in my program dynamic resource implementation or otherwise without it trying to look for it in `my project vault address` Is there a better way to try and approach this Do I need to eschew the default Vault provider entirely specify the relevant configuration parameters in my project s own namespace create the provider in my code and then manually pass that provider into every resource

red-match-15116 · Answer

Have you tried `pulumi Config vault require address `

red-match-15116 · Answer

Like to access aws region you would do ```cfg = pulumi Config aws region = cfg require region ``` So I wonder if the namespaced config is what you re missing

full-artist-27215 · Answer

Wow I m not sure how I overlooked that this is exactly what I need Thanks