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(vault): apply secret rotation error log throttling #13449

Closed
wants to merge 1 commit into from

Conversation

windmgc
Copy link
Member

@windmgc windmgc commented Aug 5, 2024

Summary

This is a simpler alternative solution for #13194. Apply error log throttling on the error logs that happened during secret rotation. Each secret will only log its error once during the period that it fails to rotate the value.

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

FTI-5775

@github-actions github-actions bot added core/pdk cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee labels Aug 5, 2024
if not ok then
self.log.warn(err)
-- throttling the error logging for secrets rotation
local add_ok, _ = SECRETS_CACHE:add(error_logging_flag_key, true)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Is it worth using cache to decrease num of log entries?

@team-eng-enablement team-eng-enablement added author/community PRs from the open-source community (not Kong Inc) and removed author/community PRs from the open-source community (not Kong Inc) labels Aug 13, 2024
@windmgc windmgc closed this Aug 22, 2024
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/pdk size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants