bitter-pharmacist-78980
10/08/2022, 2:46 PMpulumi.Run(func(ctx *pulumi.Context) error {
// Create an object store resource
bucket, err := abstractProvider.NewObjectStore(ctx, "my-object-store", nil)
if err != nil {
return err
}
})
Then, there is a separate layer which determines which provider to use or to use multiple providers for multi-cloud redundancy. (Example selection criteria: price, data center geography, real time service outages)
Does such a thing exist?
Essentially, why should a Pulumi developer need to hard code the provider into the IaC?
Also, looking at https://www.pulumi.com/blog/tag/native-providers/ it seems there has been no blog posts about native providers since the original blog post on Apr 20, 2021. Is this a sign that the native providers are not being prioritized?echoing-dinner-19531
10/08/2022, 4:17 PMDoes such a thing exist?Not really, we did start working on something like this (https://www.pulumi.com/docs/tutorials/cloudfx/) but there wasn't really much user value to it. It kinda forced targeting lowest common denominator which often wasn't enough for users.
Essentially, why should a Pulumi developer need to hard code the provider into the IaC?As above, but this is also the same for I think all other IaC tools on the market. Having said that at least it's possible with pulumi to write an abstraction like cloudfx if this did turn out to have value to someone.
Is this a sign that the native providers are not being prioritized?Not at all! Our current set of native providers continue to be worked on as a top tier providers, and we're working on improving the foundations of writing providers to make it easier for the community to start writing native-providers as well.
refined-pilot-45584
10/08/2022, 10:55 PM