sparse-intern-71089
07/13/2022, 8:08 AMlimited-rainbow-51650
07/13/2022, 8:58 AMaws-python
and aws-native-python
. We have 2 AWS providers:
• aws
- this one is a bridged terraform provider
• aws-native
- this one is a native Pulumi provider, talking to the new AWS Cloud Control API
So these templates only differ in which AWS provider is used by default.rhythmic-branch-12845
07/13/2022, 9:00 AMaws-native
, would appreciate any info if anything needs to change in terms of docs (I currently look at https://www.pulumi.com/registry/packages/aws/api-docs/)limited-rainbow-51650
07/13/2022, 9:03 AMaws-native
doesn’t provide full support yet for all AWS services, because that Cloud Control (CC) API doesn’t provide full support for all of their own services yet. So supporting more of AWS in the native provider goes at the same pace as AWS provides support for that in the CC API. But we can deliver a new version of aws-native
same day as Amazon announces new features to that API.
Still, I would suggest to go for aws-native
when it is possible, and add the classic aws
provider to the same program. You can use both in the same project (program).limited-rainbow-51650
07/13/2022, 9:05 AMrhythmic-branch-12845
07/13/2022, 9:06 AMwhite-balloon-205
pulumi new -g
which will only generate the code - it won't do any of the other initialization. That is probably the best bet if you want to have full control over dependency management.
https://www.pulumi.com/docs/reference/cli/pulumi_new/rhythmic-branch-12845
07/13/2022, 2:15 PM