Backport of Normalize all API Gateway references into release/1.15.x #16320
Conversation
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
hc-github-team-consul-core
force-pushed
the
backport/normalize-api-gateway-metadata/awfully-valid-mammal
branch
from
9ce2cff to
a594442
Compare
hc-github-team-consul-core
force-pushed
the
backport/normalize-api-gateway-metadata/awfully-valid-mammal
branch
from
c8d14ca to
501e1c2
Compare
github-team-consul-core-pr-approver
approved these changes
Feb 17, 2023
hc-github-team-consul-core
deleted the
backport/normalize-api-gateway-metadata/awfully-valid-mammal
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport
This PR is auto-generated from #16316 to be assessed for backporting due to the inclusion of the label backport/1.15.
The below text is copied from the body of the original PR.
Description
This makes sure we normalize all enterprise metadata on write across our config entries. Enterprise tests were failing with the new TLS tests due to having a mismatch between what was in a
ResourceReferenceand what was on the ConfigEntry itself as returned from the gRPC stream, as it got normalized elsewhere.Tested and validated on enterprise.
PR Checklist
Overview of commits