https://pulumi.com
Join Slack
This message was deleted.
# typescript
s
This message was deleted.
l
Why is it being created? Do you have a new Pulumi name which is different from the Pulumi name of he resource in state?
r
yes earlier it was like this
Copy code
const eksAddonCoredns = new aws.eks.Addon(
    "eksAddon",
    {
      addonName: "coredns",
      clusterName: prefix,
      resolveConflicts: "OVERWRITE",
      addonVersion: eksAddonCorednsVersion,
    },

    {
      dependsOn: [k8sCluster],
    },
  );
now it is updated like this
Copy code
const eksAddonCoredns = new aws.eks.Addon(
    "Coredns",
    {
      addonName: "coredns",
      clusterName: prefix,
      resolveConflicts: "OVERWRITE",
      addonVersion: eksAddonCorednsVersion,
    },

    {
      dependsOn: [k8sCluster],
    },
  );
this part is updated
Copy code
new aws.eks.Addon(
    "Coredns"
l
So that means that there two different resources. "eksAddon" is being deleted, and "Codedns" is being created.
Pulumi creates new resources before deleting old ones, in order reduce the risk of service interruption.
But because these are both the same resource, with the same ID, the creation fails, because you can't have 2 resources with the same AWS ID.
r
oh so i should first remove the resource and then recreate reosurce with new name is that right
l
You could, but Pulumi has a better way.
r
oh what us the better way ?
l
You can add an alias to the opts of the resource, so that Pulumi knows that the new resource is actually the old one.
➕ 1
It won't delete it.
r
oh is there link on how to add alias ?
l
Looking for it now.
10 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by