fix #4363: refining patch logic and adding metadata compare utility #4647
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.
Description
Resolves #4363 by exposing ResourceCompare.metadataChanged - a user can use that method along with an equality check of the generation or the spec to determine just exactly what if anything has been modified about a resource. Since ObjectMetadata supports an equality method, it does not seem necessary to bring the diffing logic into the api - but I did make some small refinements to that as well.
As explained in the issue it seems like a good idea to deprecate the existing ResourceCompare methods.
Type of change
test, version modification, documentation, etc.)
Checklist