millions-judge-24978
02/20/2019, 11:45 PMk8s.Provider
as an input? Taking a pulumi.Input<k8s.Provider>
runs into issues with then being able to pass it along to resources provisioned in the module.
The provider is originally a pulumi.Output<k8s.Provider>
from a different module.white-balloon-205
Pulumi.Output<k8s.Provider>
? In general, you will want to get a k8s.Provider
directly, and it should (almost always) be possible to do so.
The best way to inherit the provider is actually generally to use Components, and set all resources as parent: this
inside the component. That will the pick up the provider from the parent, allowing the component to be used with any provider (or even with the default provider) depending on how the component is created by the owner.millions-judge-24978
02/20/2019, 11:56 PMk8s.Provider
have a dependency on a sibling resource, before it may be used.this.k8sProvider = adminClusterRoleBinding.id.apply(() => k8sProvider)
white-balloon-205
Input<T>
to the inputs of the Provider, so you can create the provider using the inputs from whatever it depends on, without using apply
on those dependencies.millions-judge-24978
02/21/2019, 12:00 AMwhite-balloon-205
millions-judge-24978
02/21/2019, 12:00 AMconst k8sProvider = getProvider()
const resource = new ResourceThatMakesK8sThings("name", this, {
providers: { kubernetes: k8sProvider }
})
opts?: pulumi.ComponentResourceOption
, used in the super
callwhite-balloon-205
millions-judge-24978
02/21/2019, 12:10 AMsuper
call?