Skip to content
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

Remove ForceNew on repo and chart changes #253

Merged
merged 4 commits into from
Aug 26, 2019

Conversation

lawliet89
Copy link
Contributor

@lawliet89 lawliet89 commented Apr 16, 2019

Fixes #173

helm upgrade does not delete the release when the chart/repo are changed. The Helm provider should not too.

I tested this by changing a chart/repo and the upgrade worked fine.

@lawliet89
Copy link
Contributor Author

@rporres @meyskens Any thoughts on this other than radio silence?

@legal90
Copy link
Contributor

legal90 commented Jun 15, 2019

@rporres @meyskens Could you please review this PR?

@legal90
Copy link
Contributor

legal90 commented Jul 9, 2019

@rporres @meyskens @alexsomesan Could anyone review this PR and provide the feedback?

IMO, it totally makes sense to remove ForceNew flag from chart and repository parameters, since helm handles such updates of existing releases.

@Starefossen
Copy link

We have been hit hard by this one lately. Anything we can do to help moving this forward?

@rporres
Copy link

rporres commented Aug 26, 2019

Apologies, this had fallen off my radar. Makes total sense.

@rporres rporres merged commit 2c0efe6 into hashicorp:master Aug 26, 2019
@ghost ghost locked and limited conversation to collaborators Apr 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

New resource shouldn't be required when a chart is updated
4 participants