[backport -> release/3.8.x] fix(*): reject config if both deprecated and new field defined and their values mismatch #13594
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.
Automated backport to
release/3.8.x
, triggered by a label in #13565.Original description
Summary
This PR adds a validation to deprecated fields that checks the case in which both new field and old field were defined; when that happens their values must match.
It introduces a new structure to deprecation definition by adding
replaced_with
information. This way field validation can verify if thereplaced_with
field has the same value as the old deprecated field. By default the comparison is done via translation through simple path but there might be instances where translation from old to new is more complicated and then the translation function should be provided intranslation
field.The plan is to remove
translate_backwards
field in the future in favor ofreplaced_with
.Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.mdIssue reference
KAG-5262