What s the coverage like for the aws native provider compare

Question

What s the coverage like for the aws native provider compared to the tf based provider Good enough to switch

red-match-15116 · Answer

not exactly depending on your use case <https pulumi community slack com archives C84L4E3N1 p1634140782087300 thread ts=1634118479 073900 amp cid=C84L4E3N1>

little-cartoon-10569 · Answer

It s already better for some things EC2 image builder for example

little-cartoon-10569 · Answer

Best right now to switch on a case by case basis only

little-summer-88406 · Answer

Poor Subnets for example are marked Deprecated with the message not implemeneted VPCs or perhaps it was SGs too iirc S3 Bucket Policy too Loads of stuff not implement not just esoteric parts

little-summer-88406 · Answer

Hoping 0 2 0 is better pushed to GH a few days ago but marked unreleased as of yesterday

little-summer-88406 · Answer

Whilst true that you can kinda of mix and match in terms of using outputs of awsnative resource arn id as inputs to aws but the big issue I see is there is no easy way to later migrate from aws tf to awsnative aliases etc dont cover this scenario

little-summer-88406 · Answer

Problem is a lot of stuff in the AWS tf is buggy potentially due TF so not blaming Pulumi and for the APIs currently supported work flawlessly in awsnative So it s a difficult time to onboard Pulumi AWSNative should of had the alpha label instead of marketing writing the blog imo

little-summer-88406 · Answer

I guess you could later use importids to brings across all the aws tf stuff on a completely fresh proj stack on awsnative as long as you can get all the props identical so no diff can see this being a challenge

little-summer-88406 · Answer

Luckily at this stage we re just building dev stacks so Im hoping by time we come to do production AWSNative is in good shape i e we d destroy aws tf native hybrid monster and just deploy a fresh project all on awsnative