Every time I think I think I have this sorted out I realize

Question

little-cartoon-10569 · Answer

Can you convert this to a text snippet It s a huge post moving the code to a snippet makes it collapse which makes browsing the channel easier

little-cartoon-10569 · Answer

There shouldn t be any need for the provider to be apply ed And provider should almost never be an arg It should be available through opts usually

cuddly-flower-91328 · Answer

Ok 1 sec

cuddly-flower-91328 · Answer

Here we go

little-cartoon-10569 · Answer

This looks like code in a ComponentResource Was args provider created via `new k8s Provider ` or similar You should be passing these sorts of providers in via opts Hopefully there ll be a way to avoid creating this Deployment inside an `apply ` it s never good to create resources inside an apply and it s almost always avoidable

little-cartoon-10569 · Answer

For example changing ```` node group auto discovery=asg tag=```` to ```pulumi interpolate` node group auto discovery=asg tag=```` would mean you can remove `clusterName` from the apply

little-cartoon-10569 · Answer

That is assuming that command is an array of Input lt string gt If it s not you can still use apply around the lowest level that does handle Inputs Let me check the API docs

little-cartoon-10569 · Answer

Confirmed that command is suitable for this syntax ```command pulumi Input lt pulumi Input lt string gt gt ```

little-cartoon-10569 · Answer

I wish they d put Input Output back into the API docs there s plenty of times when knowing that something is `Input lt Input lt string gt gt ` is important presenting it in the API docs as `string ` hides important information

cuddly-flower-91328 · Answer

Thanks < little cartoon 10569> A colleague and myself were just talking about the provider today and whether passing as an opts on a ComponentResource would be better but I hadn t tested a different approach yet Would provider be inherited or would I access it via `opts provider` instead

little-cartoon-10569 · Answer

It s not implicitly inherited afaik but best practice is to pass the ComponentResource s opts to every child resource Generally only the parent property needs to change Somethings the protect property

little-cartoon-10569 · Answer

The only time you need to be careful is if your ComponentResource groups resources with different providers You should probably check at the top of the constructor that all the required providers are included

little-cartoon-10569 · Answer

I usually store opts as a member property this opts and define `private parentOpts parent Resource return this opts parent parent `

cuddly-flower-91328 · Answer

Great Thanks so much

limited-rainbow-51650 · Answer

If you want to pass a custom provider to a component resource make sure to use the `providers` plural resource option See the docs on this <https www pulumi com docs intro concepts resources components inheriting resource providers> Within the implementation of your component you do not have to pass the provider s to your child resources You do have to set the `parent` option on the child resource pointing to the component Provider lookup always starts at the resource itself and traverses the parent link via the component all the way up to the stack resource Each resource without an explicit parent has the stack as its implicit parent where the default provider is resolved

cuddly-flower-91328 · Answer

Thanks < limited rainbow 51650>