[TEST] yaml-diff: key reorder only (no value change)#133
Closed
weatherhog wants to merge 1 commit into
Closed
Conversation
Exercises the yaml-diff bot: keys reordered, values identical. Expect dyff to report no semantic difference while yamllint key-ordering fails. Throwaway test PR for roadmap#4121.
|
No semantic YAML differences in changed source files. (Key reordering without value changes is ignored.) Suppress with |
Contributor
Author
|
Closing — throwaway Phase-1 verification PR for roadmap#4121. All the work it exercised is merged: the yaml-diff bot, the SOPS-exclusion fix (giantswarm/github-workflows#231), colour output (#232), and the CI extraction (#233 + #139). Key-ordering removal is in #140. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Throwaway test PR for the yaml-diff bot rollout — roadmap#4121. Do not merge; close after verifying.
What this tests
Top-level keys of one ConfigMap are reordered (
kind/apiVersion/metadata/data), no values changed.Expected
yaml-diffbot comment: "No semantic YAML differences" (dyff--ignore-order-changes).validate/ yamllint failskey-ordering— this is expected and is exactly the friction #4121 is about. It demonstrates the bot correctly sees a no-op while the lint rule still rejects the reorder, which is the case for droppingkey-ordering: {}in phase 2.