clean-dentist-251511/16/2020, 9:41 PM
The resource provider for a custom resource is determined based on its package name. For example, theAFAICT "package name" means likepackage will load a plugin named
aws, and the
pulumi-resource-awspackage will load a plugin named
kubernetes. Each provider uses the configuration from its package to alter its behavior.
i.e. https://github.com/pulumi/pulumi-kubernetes/ the parent of the
so I guess the standard package naming scheme changed since those docs? And... the point of all this is... a kind of dependency injection? so in the keda example we're injecting a specific instance of the kubernetes provider, rather than letting
use the one from https://github.com/pulumi/pulumi-kubernetes/blob/master/sdk/nodejs/provider.ts which it otherwise would?