-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm Chart v4: graceful migration from v3 #3110
Comments
Sorry for the inconvenience, it is an aspect we'd like to improve upon. A possible workaround is to use a transform function to apply an "alias" option to each child. The alias option lets you "move" a resource by defining its prior parent URN and its prior name. |
Since I don't want to bloat the "codebase" with aliases everywhere I have resorted to stuff like:
The issue is that Chart v4 adds the release name to all resources compared to Chart v3 so |
We'd like to add some documentation around how to accomplish this using transforms since it's fairly involved. |
this helped me to migrate: in the v4 in the ComponentResourceOptions I am using something like this: {
parent: this,
aliases: [{type: "kubernetes:helm.sh/v3:Chart"],
transforms: [args => {
return {
props: args.props,
opts: pulumi.mergeOptions(args.opts, {
aliases: [{ parent: "<urn of the helm v3 resource>"}]
})
};
}],
} // quite a recent versions of @pulumi/kubernetes and @pulumi/pulumi required as of today update: I have just noticed the "aliases" is not required, transforms are enough |
Hello!
Issue details
I'm trying to migrate from the helm Chart resource v3 to v4, but pulumi wants to redeploy the helm charts, and since it creates new resources before deleting old ones I get name conflicts.
There should be a clean migration path.
Personally I would be grateful even of a
pulumi stack export [...] && sed [...] && pulumi stack import
solution.Affected area/feature
kubernetes.helm.v4.Chart
The text was updated successfully, but these errors were encountered: