Hi all I am setting up our IoT infra in aws and there seems

Question

Hi all I am setting up our IoT infra in aws and there seems to be quite a bit missing from the pulumi aws package provisioning things group job template just making sure I did not miss something

great-sunset-355 · Answer

`pulumi aws` == if it s missing in terraform it s missing in pulumi same goes for API all good and bad things from terraform API are transferred over to pulumi

great-sunset-355 · Answer

I did some aws IoT with cdk but even then I had to create custom resources to talk to IoT API because it s not implemented in CloudFormation either judging from this same will be true for terraform and pulumi I m guessing you d need to extend fork `pulumi aws` provider yourself I d love to see some examples of this myself Maybe < billowy army 68599> can nudge us in a good direction

billowy-army-68599 · Answer

you re correct we bridge the pulumi aws provider from the terraform provider We re building a native AWS provider but we don t have an ETA yet

billowy-army-68599 · Answer

if you want to support a resource that isn t supported in the provider you can either ask them to merge the changes upstream in which case you ll get it in pulumi use a dynamic provider example here <https www twilio com blog intro to infrastructure as code with twilio part 1> build a native provider just for that resource

great-sunset-355 · Answer

I was just reading this example <https github com pulumi examples tree master twilio ts component> Do I understand correctly that it shows a custom component resource without dynamic provider simply using SDK to call Twilio API

billowy-army-68599 · Answer

that s not a dynamic provider

billowy-army-68599 · Answer

there are dyanmic providers here <https github com pulumi examples search l=Python amp q=dynamic>

helpful-knife-18557 · Answer

I ll look over this tomorrow and reports what i come up with as this is fairly critical for us Thanks < great sunset 355> and < billowy army 68599>

helpful-knife-18557 · Answer

so sounds like Dynamic provider might be the best approach here At glance it does not sounds too complex Ill give it shot So would best practice be to create a provider per missing IoT feature or one larger aws iot extra provider

helpful-knife-18557 · Answer

think i got my answer one per missing feature

helpful-knife-18557 · Answer

So conclusion Dynamic provider did do the job pretty well using Boto3 under the cover pretty simple in the end well done Pulumi