This message was deleted.
# announcementss
sparse-intern-71089
08/30/2023, 4:01 PMThis message was deleted.
m
millions-furniture-75402
08/30/2023, 4:03 PMFYI "Release Notes" link is 404 https://github.com/pulumi/pulumi-aws/releases/tag/v6.0.0
r
rough-morning-53309
08/30/2023, 4:11 PMThanks @millions-furniture-75402! Let me correct that 🙂
✅ 1
l
little-library-54601
08/30/2023, 5:15 PMIs there anyplace that details the concept of "Classic" vs. "Native" providers - not just from AWS perspective, but in general (e.g. would also apply to Azure Classic vs. Native)?
The little I've been able to pick up made me think that once a "native" provider existed for a cloud service, any "classic" provider there might have been would at that point be deprecated.
Sounds like at least for AWS, that's not the case. So how are we to think about these things?
m
millions-furniture-75402
08/30/2023, 5:18 PMClassic means it's based on the terraform provider. Native means a provider that was developed Pulumi-first and I believe they all use the Cloud provider APIs that describe their SDKs (e.g. AWS CloudControl API) to generate the Provider SDKs.
✔️ 1
😲 1
millions-furniture-75402
08/30/2023, 5:20 PMIf you can move entirely to the Native providers, you should because the benefit is faster updates to SDKs. Depending on your use case, you may want to stay on classic, or mix classic and native.
l
little-library-54601
08/30/2023, 5:25 PMFrom Pulumi's perspective, what's the benefit to enhancing a "classic" provider once a native provider exists?
m
millions-furniture-75402
08/30/2023, 5:27 PM1. Coverage differences. The classic providers had A LOT more coverage last time I checked.
2. Customers depend on it. If things start to break because Pulumi isn't maintaining the libraries many of the their customers use, then Pulumi's product looks poor