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

Display values diff on upgrade #40

Merged
merged 1 commit into from
Apr 19, 2020
Merged

Display values diff on upgrade #40

merged 1 commit into from
Apr 19, 2020

Conversation

dtuite
Copy link
Member

@dtuite dtuite commented Apr 9, 2020

  • Display a diff when a chart is upgraded or rolled back.
  • Put this behind a flag and disable it by default to protect leaks
  • Add the config in the readme.
  • Add in the config in the docs.
  • Add a blacklist or whitelist solution.

@dtuite dtuite linked an issue Apr 9, 2020 that may be closed by this pull request
@dtuite dtuite self-assigned this Apr 9, 2020
@dtuite dtuite marked this pull request as draft April 9, 2020 21:11
Only show diff if non-empty string

 - Disabled by default to prevent sensitive values from being leaked.
 - Also changed website in Chart.yaml
 - Added to readme
@dtuite dtuite marked this pull request as ready for review April 19, 2020 16:14
@dtuite dtuite merged commit 028c9e4 into master Apr 19, 2020
@dtuite dtuite deleted the diff-values branch April 19, 2020 16:15
@@ -38,6 +41,8 @@ func (e *Event) Init() error {
e.currentRelease = e.GetRelease(e.CurrentReleaseSecret.Name)
e.previousRelease = e.getPreviousRelease()

e.GetConfigDiffYAML()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why call this if you don't capture the return value

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. That's a mistake. I was just forcing it to run during development so the diff would be logged. I removed the log line but forgot to remove this.

I wasn't expecting anyone to review it so I just merged it to master but I will remove this now.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to tackle the issue with sensitive values being leaked in a separate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Output helm values diff
2 participants