Python - Unable to specify EKS version after cluster resource created

[Raggey]

What happened?

When using EKS cluster and updating version property, resource wants to re-create as ARN changes. Seems to be an issue pulling and comparing the current EKS version.

Pulumi preview shows: aws-native:eks:Cluster XXX update [diff: +version]

Did some digging into the verbose logs:
Marshaling property for RPC[Provider[aws-native,].Diff(urn:###).olds]: version={1.21}
Marshaling property for RPC[Provider[aws-native, ].Diff(urn:###.news]: version={1.21}
step_generator.go:840] Planner decided to update '###' diff: version:{1.21}])

Steps to reproduce

• Existing EKS cluster without version prop (Cluster defaults to latest version)
• Attempted to specify version property with as current version in pulumi stack / EKS
• Pulumi detects a diff as new prop is passed and attempts to re-create the resource and resource ARN

Expected Behavior

Resource shouldn't have a diff, and should be able to update in place.

Actual Behavior

Pulumi detects a diff as new prop is passed and attempts to re-create the resource and resource ARN

Versions used

3.24.1and 3.30.0

CLI
Version 3.24.1
Go Version go1.17.6
Go Compiler gc

Host
OS ubuntu
Version 21.04
Arch x86_64

Additional context

Workaround I found was to manually update the stack json to set the input property version to the current version on EKS.
However, error re-occurs when trying to update the version property to a new EKS version.

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).