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.

Pulumi Community

Hi. I'm getting a
`"TypeError: AddonArgs.__init__() got an unexpected keyword argument 'resolve_conflicts_on_create'"` 
when using `aws.eks.Addon`( what is the version dependency here? on one of the pulumi modules?
Thanks

Are you able to share the relevant portion(s) of your code?

```vpc_cni_addon = aws.eks.Addon(f"{self.stack_name}-vpc-cni-addon",
            aws.eks.AddonArgs(
                cluster_name=cluster.eks_cluster.name,
                addon_name="vpc-cni",
                addon_version=pulumi.Config().require("vpc_cni_version"),
                resolve_conflicts="OVERWRITE",
                # resolve_conflicts_on_create="OVERWRITE",
                # resolve_conflicts_on_update="OVERWRITE",
            ),
            opts=pulumi.ResourceOptions(parent=cluster,provider=self.aws_provider, custom_timeouts=pulumi.CustomTimeouts(create="3m")),
        )```
Commented out
```  # resolve_conflicts_on_create="OVERWRITE",
 # resolve_conflicts_on_update="OVERWRITE",```
which work with versions
`pulumi             3.96.2`
`pulumi-aws         6.13.3`
`pulumi-aws-native  0.90.0`
`pulumi-awsx        2.3.0`
`pulumi-docker      4.5.0`
`pulumi-eks         2.0.0`
`pulumi-kubernetes  4.5.5`
```resolve_conflicts="OVERWRITE",```
works with versions
`pulumi             3.51.0`
`pulumi-aws         5.26.0`
`pulumi-aws-native  0.90.0`
`pulumi-awsx        1.0.1`
`pulumi-docker      3.6.1`
`pulumi-eks         1.0.3`
`pulumi-kubernetes  3.23.1`

Hope that makes sense.

I think you're probably just seeing a slight difference in the behavior of the providers; in the first case, you're using AWS Classic v6, AWSX v2, and EKS v2; these are all major version upgrades from the latter case. I would guess that if we check the changelogs we'd probably find that `resolve_conflicts` in the older providers is now `resolve_conflicts_on_create` and `resolve_conflicts_on_update` in the newer providers.

Yeah, I started to wade through the changelogs:-) Thanks!