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

Transform values files in profiles to v1alpha3 #1070

Conversation

GeertJohan
Copy link
Contributor

I made a mistake in #985. With the v0.15.0 skaffold fix the valuesFilePath field in profiles is completely dropped. These changes fix that.

These changes are based on the v0.15.0 tag. I think this PR shouldn't actually point to master but to a v0.15.x branch from which we may release v0.15.1

Apologies for the inconvenience. I hope it's possible to push out a hotfix release fast.

@codecov-io
Copy link

Codecov Report

Merging #1070 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1070   +/-   ##
=======================================
  Coverage   40.86%   40.86%           
=======================================
  Files          70       70           
  Lines        3091     3091           
=======================================
  Hits         1263     1263           
  Misses       1703     1703           
  Partials      125      125

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3ec4835...06b0e15. Read the comment docs.

Copy link
Contributor

@balopat balopat left a comment

Choose a reason for hiding this comment

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

Thanks for filling this back in :)
Can you please write a test for this?
Thank you!

@GeertJohan
Copy link
Contributor Author

GeertJohan commented Oct 1, 2018

@balopat Was already looking at that, but tests for the transform seem to be missing completely so it'll take a bit more time.

edit: Actually I'm not sure what would be the best approach to test the transform functions.. I suggest a string comparison; input A, expect B. Would that be sufficient?

@balopat balopat added the kokoro:run runs the kokoro jobs on a PR label Oct 1, 2018
@kokoro-team kokoro-team removed the kokoro:run runs the kokoro jobs on a PR label Oct 1, 2018
@balopat
Copy link
Contributor

balopat commented Oct 1, 2018

Yeah, I think with transformation logic we could go as thorough as covering quick-check style a lot of combinations, or the lazy way is to provide a couple of full golden examples and provide some coverage.

We do have a "the conversion doesn't fail and the result is deployable" test at https://github.com/GoogleContainerTools/skaffold/blob/master/integration/run_test.go#L224 but that should already cover your case.

And with that, I'm going to unblock this PR. I think we should improve the test coverage on these though on the long run or do a better validation integration test.

@balopat balopat merged commit 600f25b into GoogleContainerTools:master Oct 1, 2018
@GeertJohan GeertJohan deleted the hotfix/value-files-in-profiles branch October 2, 2018 09:30
@GeertJohan GeertJohan restored the hotfix/value-files-in-profiles branch October 2, 2018 09:30
@GeertJohan
Copy link
Contributor Author

@balopat Can we release this hotfix as v0.15.1? Otherwise users will break their skaffold.yaml when switching to v0.15.0 and v0.16.0 is still a few weeks away I guess?
cc @r2d4

@balopat
Copy link
Contributor

balopat commented Oct 2, 2018

Yes, I will work on the v0.15.1 release today!

@balopat balopat mentioned this pull request Oct 2, 2018
balopat pushed a commit to balopat/skaffold that referenced this pull request Oct 2, 2018
@GeertJohan GeertJohan deleted the hotfix/value-files-in-profiles branch October 3, 2018 08:56
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.

4 participants