Hi all! Sorry if that was already discussed, but I couldn't find answer anywhere. As of <https://git...
e
eager-church-17824
12/26/2024, 9:45 AMHi all! Sorry if that was already discussed, but I couldn't find answer anywhere. As of https://github.com/pulumi/pulumi-aws-native/pull/1750 AWS Cloud Control plugin (FKA aws-native) is no longer promoted to be used for new projects:
> For new projects, we recommend using AWS Native and AWS Classic side-by-side so you can get the speed and correctness benefits of AWS Native where possible.
Became:
> For new projects, we recommend starting with our primary AWS Provider and adding AWS Cloud Control resources on an as needed basis.
That caught me by surprise, as we were doing the former - using AWS Cloud Control plugin and using AWS Classic only when we could not get AWS CC to work. Now it reads as if we should stick to AWS Classic only. I might be missing something but as AWS Classic covers all the resources, seems like "as needed basis" will never be the case.
Can anybody elaborate whenever it's safe to assume that AWS CC provider will eventually become the primary provider? Or should we stop bothering about it and just stick to AWS classic one?
q
quaint-hydrogen-7228
12/26/2024, 4:58 PMIMHO, that is a pragmatic change to not have the aws cc provider as the primary one, as that depends on AWS actually providing support for all their services through the cloud control api - which they do not.
e
eager-church-17824
12/26/2024, 5:00 PMI am more confused about the as needed basis. In our use case AWS Classic covers 100% of cases, so Cloud Control API based one is never needed. So it feels like aws-native is redundant in this case.
eager-church-17824
12/26/2024, 6:00 PMAnd (full disclosure) we had a bit harder time with aws-native in some cases. On the other hand, security groups referring to each other are almost impossible with AWS classic 😄 So I guess I have answered my own question LOL
l
little-cartoon-10569
12/26/2024, 7:19 PMI use security groups that refer to each other as a matter of course. Just don't use inline rules.
e
eager-church-17824
12/26/2024, 8:26 PM@little-cartoon-10569 Oh! By some reason I was not aware that AWS classic has same feature. Awesome! Thank you!
b
better-kitchen-49894
12/27/2024, 8:27 AM@eager-church-17824 I guess as needed would be some corner cases where the classic provider does not provide coverage but cc provider does, or you need some feature before it is implemented in classic provider.
Technically the Cloud Control API could be used with 3rd party (not AWS) resources exposed via Cloud Control API, although in Pulumi's case that would likely be done via a provider for that 3rd party instead.
Pulumi CDK uses the CC provider under the hood for code that you build with AWS CDK libraries to use with Pulumi.
e
enough-garden-22763
12/27/2024, 2:52 PMCan anybody elaborate whenever it's safe to assume that AWS CC provider will eventually become the primary provider
enough-garden-22763
12/27/2024, 2:54 PMI would not assume that. The messaging update you caught was attempting to stop giving the impression that AWS CC will replace Classic. We are committed to maintaining both but objectively AWS Classic as of today is the recommended option as it just works better for most users.
enough-garden-22763
12/27/2024, 2:54 PMOne interesting use case for AWS CC in the Pulumi ecosystem is it use in the CDK bridge https://github.com/pulumi/pulumi-cdk that allows to provision CDK constructs on top of Pulumi.
e
eager-church-17824
12/27/2024, 5:11 PMThank you everyone! That clears things out for me!
Pulumi Community
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.
Powered by