https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
b
I'm unsure of the specifics of your problem, but just an FYI that there are no inherent issues with using both providers if doing so would solve your problem in the meantime
💯 2
a
I get a dependency message... - see https://github.com/pulumi/pulumi-eks/issues/674
b
Ah, OK. I misunderstood and spoke too quickly. Sorry about that. It looks like pulumi needs to do a new release of 
pulumi-eks
Are you able to use the AWS Native provider to solve your elastic cache issues, so that you can keep your AWS Classic provider <5.0 for now? I suspect the reason why 
pulumi-eks
hasn't released is because they are focusing on aws-native and I would expect them to have plans to migrate pulumi-eks to use aws-native instead of classic
It's obviously in public preview still so if you don't want to use aws-native yet for that reason I would understand, but just a thought.
a
I have not tried AWS-native yet in a bigger scale... I guess the two editions (classic and native) should work fine together as they really interchange various AWS IDs.
b
yes you should be able to use aws-native and aws-classic alongside eachother without issues
and given that aws-native is generated from Cloud Control APIs I would expect it to have the up-to-date APIs for the elasticcache resources
👍 1
3 Views
Open in Slack
PreviousNext
Powered by