-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Emit a warning on build when deprecated fields are used #4723
Merged
k8s-ci-robot
merged 1 commit into
kubernetes-sigs:master
from
koba1t:emit_a_warning_when_deprecated_fields_are_used
Nov 16, 2022
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we sure this is going to work, given that
FixKustomizationPreUnmarshalling
above mutates the file to accommodate some of the deprecated fields?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like
FixKustomizationPreUnmarshalling
is fixing for raw[]byte
data before unmarshaling to yaml.kustomize/api/types/fix.go
Lines 12 to 32 in f61b075
I think this function doesn't affect some of the deprecated fields in
Kustomization
struct.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interestingly, this changes
imageTags
toimages
, which is a deprecation I wasn't even aware of. Also, it makes it seem like the field calledpatchesStrategicMerge
was originally calledpatches
, and we later re-introducedpatches
with a different meaning. 🤦Ideally, I think we should warn about
imageTags
too, so we can get rid ofFixKustomizationPreUnmarshalling
along with all the deprecated fields.Also, I wonder if folks using the super old version of
patches
would get a weird warning aboutpatchesStrategicMerge
(which they aren't using) because of this method. Can we check this please?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is hard to delete the
FixKustomizationPreUnmarshalling
function while we support the super old version of patches.Because super old
patches
(It is calledpatchesStrategicMerge
today) have a different struct to today'spatches
field.I think we will get an error when unmarshaling
[]byte
toKustomization
struct if we delete the pre unmarshalling process.kustomize/api/types/kustomization.go
Lines 66 to 76 in 4fc0249
kustomize/api/types/patchstrategicmerge.go
Line 9 in 4fc0249
kustomize/api/types/patch.go
Lines 8 to 24 in 4fc0249
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is right. If we use very old style
patches
, the warning message ofpatchesStrategicMerge
appear...