No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi <@U02KDCRKE73>,

The AWS Native provider is in a public preview state and the recommendation is to use side-by-side AWS Native and AWS Classic as described in the “<https://www.pulumi.com/registry/packages/aws-native/|Note>”
However, I’m using AWS Native as much as possible and most of my code is using Native than Classic.

I am also using native for initial resources but very often find a resource not available and have to import classic and native in the same package.

you got any info of the updated status of this package?. I wonder why Azure/GCP got their native package quicker than aws, taking a wild guess it seem is on how AWS i exposing their resources.

Hi <@U02KDCRKE73>,

To be honest with you, I guess that is a common difference between providers that don’t need to be developed together. We can have a stable Azure Native provider and an AWS Native provider in a different state. You can check in public Pulumi Roadmap the progress of each component, provider, etc.: <https://github.com/orgs/pulumi/projects/44/views/4>. Another source that I use frequently is the Release comparison to understand if a specific issue was gone: <https://github.com/pulumi/pulumi-aws-native/compare/v0.19.0...master>. If we can have a proper release note, it will be better than this method, which is a bit complex, but it is what we have right now. In my personal TODO, I want to contribute to improving that area.
About the code, I can’t see the issue in using AWS Native and AWS Classic together because I’m using it, I guess most engineers are in the same boat. Standardising the IaC using only one will be better but is acceptable to have this transition.

<@U01FHMA71BK> yeah I agree. But will the classic be deprecated at some point?. I will take a look at the progress you mentioned.

<@U02KDCRKE73> I’m not sure what’s Pulumi long-term plans but based on the history of the Pulumi community they listen to us all the time and if it will be deprecated we will be informed in a reasonable time to prepare our code/workloads. 

<@U02KDCRKE73> The AWS Native package depends on AWS Cloud Control API, which is a relatively new API from AWS. What is supported really depends on AWS in the end.