10/02/2021, 7:11 PM
Hello everyone, question regarding Dynamic Resource Providers. With typical resource providers like AWS, at least in the case of Terraform and according to my understanding, the provider itself merely handles auth and general configuration that is applicable to all downstream API calls while the resources themselves seem to handle the details of how to CRUD which kinda makes sense as the provider would otherwise be a massive switch statement. In Pulumi and with dynamic resource providers, it seems the right usage pattern is to have a one to one mapping between the dynamic provider and the resource it manages Am I understanding this correctly? For example, if I were to build a resource provider to support provisioning a Database and a User in fictitious database server then I would end up with two dynamic providers for each kind of resource and not one provider that can handle both resources?