abundant-computer-36798
12/06/2022, 5:15 AMawsx.elasticloadbalancingv2.NetworkListener
, but this no longer exists. I think it moved from awsx
to aws
at some point, to aws.elasticloadbalancingv2.Listener
. (Could someone verify / explain what falls under awsx
vs aws
?) And then I find out from the docs that now this is deprecated in favor of aws.lb.Listener
, so I should really be using that?
And to further the confusion, I learn that everything under @pulumi/aws
is known as classic, and if I want to stay modern I should actually be using @pulumi/aws-native
instead of any of the options above? Incredibly, although elasticloadbalancingv2
got renamed to lb
in classic, it's back to being called elasticloadbalancingv2
in native!fierce-ability-58936
12/06/2022, 10:04 AMawsx
to aws
, because the aws
package reflects resources from the corresponding terraform aws provider.
awsx
is a wrapper around that aws
provider that provides you with some sensible defaults and allows to get started quickly. It's not a separate thing, it just complements the original aws
provider.
Ok, so now the classic / native. The classic aws
package utilises the terraform provider, with its convenience hacks (like a security group association resource, which is not a real resource).
Whenever a new service appears from AWS, or an existing one gets a new feature, it has to go through the aws terraform provider development cycle, to be included later on into the Pulumi's aws provider, which will just update the terraform provider version under the hood.
The Pulumi's "native"-type providers are created differently. They're generated from the API specs, and can be quickly regenerated whenever there's a change in the spec. Then are much leaner in a sense and allow to bring new features quickly.
Which one to use? Depends on the use case. I'd still have the classic aws
as the base, and add aws-native
if there's a feature I need, which doesn't exist in the former yet.
Disclaimer: I'm not affiliated with Pulumi org, I'm just a fellow Pulumi user who likes processing information 😄 If I made any wrong statements or assumptions, please correct me!abundant-computer-36798
12/07/2022, 8:05 PMfierce-ability-58936
12/07/2022, 8:29 PM