Skip to content
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

[backport -> release/3.7.x] fix(plugins): add realm to removed fields #13127

Merged
merged 1 commit into from
Jun 11, 2024

Conversation

team-gateway-bot
Copy link
Collaborator

Automated backport to release/3.7.x, triggered by a label in #13042.

Original description

Summary

Basic-auth and key-auth added new field "realm" but it was not added to "removed_fields" which breaks backwards compat between new CPs and old DPs. Adding realm to removed fields fixes the issue.

Checklist

  • The Pull Request has tests
  • A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
  • There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

KAG-4516

@nowNick nowNick force-pushed the backport-13042-to-release/3.7.x branch from 9c968ca to b46dce7 Compare June 10, 2024 11:51
Basic-auth and key-auth added new field "realm"
but it was not added to "removed_fields" which breaks backwards compat
between new CPs and old DPs. Adding realm to removed fields
fixes the issue.

KAG-4516

(cherry picked from commit 420b3b6)
@nowNick nowNick force-pushed the backport-13042-to-release/3.7.x branch from b46dce7 to 07cdecb Compare June 10, 2024 12:12
@bungle bungle merged commit d7a25df into release/3.7.x Jun 11, 2024
25 checks passed
@bungle bungle deleted the backport-13042-to-release/3.7.x branch June 11, 2024 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee core/clustering size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants