This message was deleted.
# typescript
s
This message was deleted.
l
awsx is a collection of mixins and component resources that provide some convention-over-configuration conveniences.
It uses aws underneath. You can migrate resources between the two libraries, but it can be tricky because of re-parenting / aliasing.
awsx is great for getting started, proofs-of-concepts, and any code that you don't intend to manage in production for an extended period.
d
Oh. So the preference is aws?
l
If you need fine-grained control over your resources, then you should prefer aws, if you have to time to create all the resources yourself.
This is my opinion, at least.
d
Ah. Ok. Good to know. Trying to resolve my first issue (12:54pm) was thinking that maybe I wasn’t using the latest provider.
Actually, scratch that, I’m now trying to use aws-native where I can instead of aws.
l
They're compatible. You can mix and match.
If you create a VPC in one, you can pass that VPC ID into a constructor of the other.
d
I’m just trying to replace a TargetGroup without success.
Doesn’t like to be renamed.
Ugh. Same issue with aws-native as aws original flavor.
l
Yes, that's an AWS thing. It's highlighted in the Pulumi docs with the little icon next to the name property.
That icon means that replacement will happen if the property changes. Can't be worked around.
s
Just to augment what @little-cartoon-10569 said, all AWSX 1.0 (currently in beta) features are full multi-language components, no single-language overlays, so going forward you'll get the same experience in all supported Pulumi languages.
d
That’s fine. I don’t mind it being replaced, it just fails at replacing it.
Apparently it’s a bug from 2020 https://github.com/pulumi/pulumi/issues/5900
l
d
I’m not sure that would have worked for me but maybe I’ll try to reproduce. At the moment I fixed my issue manually so I could move on to other things.