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

fix(runloop): the sni cache isn't invalidated when a sni is updated #13165

Merged
merged 1 commit into from
Jul 11, 2024

Conversation

catbro666
Copy link
Contributor

@catbro666 catbro666 commented Jun 5, 2024

Summary

Both data.entity and data.old_entity should be invalidated when a sni is updated. A non-existent sni may also have been cached.

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

https://konghq.atlassian.net/browse/FTI-6009

@github-actions github-actions bot added core/proxy cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee labels Jun 5, 2024
kong/runloop/events.lua Outdated Show resolved Hide resolved
@catbro666 catbro666 force-pushed the fti-6009-sni-cache-invalidate branch from e91931e to 7ff3071 Compare June 5, 2024 09:10
bungle
bungle previously requested changes Jun 5, 2024
kong/runloop/events.lua Outdated Show resolved Hide resolved
@catbro666 catbro666 force-pushed the fti-6009-sni-cache-invalidate branch from 7ff3071 to 9c8cd54 Compare June 6, 2024 03:11
@catbro666 catbro666 requested a review from bungle June 6, 2024 03:17
kong/runloop/events.lua Outdated Show resolved Hide resolved
Both `data.entity` and `data.old_entity` should be invalidated when
a sni is updated. A non-existent sni may also have been cached.

https://konghq.atlassian.net/browse/FTI-6009
@catbro666 catbro666 force-pushed the fti-6009-sni-cache-invalidate branch from 9c8cd54 to 769b031 Compare June 13, 2024 07:39
@windmgc windmgc merged commit 989a13e into master Jul 11, 2024
25 checks passed
@windmgc windmgc deleted the fti-6009-sni-cache-invalidate branch July 11, 2024 07:31
@team-gateway-bot
Copy link
Collaborator

Cherry-pick failed for master, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally.

git remote add upstream https://github.com/kong/kong-ee
git fetch upstream master
git worktree add -d .worktree/cherry-pick-13165-to-master-to-upstream upstream/master
cd .worktree/cherry-pick-13165-to-master-to-upstream
git checkout -b cherry-pick-13165-to-master-to-upstream
ancref=$(git merge-base 50f5a37a41325f92a367f25bcdf6cd58fd399960 769b031b6ff56265cfbbf36fd7aaf31720d21dcc)
git cherry-pick -x $ancref..769b031b6ff56265cfbbf36fd7aaf31720d21dcc

@github-actions github-actions bot added the incomplete-cherry-pick A cherry-pick was incomplete and needs manual intervention label Jul 11, 2024
@windmgc
Copy link
Member

windmgc commented Jul 11, 2024

@catbro666 Please handle cherry-pick manually

@catbro666
Copy link
Contributor Author

@catbro666 Please handle cherry-pick manually

done.

@locao locao removed the incomplete-cherry-pick A cherry-pick was incomplete and needs manual intervention label Jul 16, 2024
oowl pushed a commit that referenced this pull request Aug 15, 2024
…13165)

Both `data.entity` and `data.old_entity` should be invalidated when
a sni is updated. A non-existent sni may also have been cached.

https://konghq.atlassian.net/browse/FTI-6009
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/proxy size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants