auth api: flush all caches when flushing - #13514
Merged
Merged
Conversation
omoerbeek
reviewed
Nov 20, 2023
Pull Request Test Coverage Report for Build 7226248045
💛 - Coveralls |
Contributor
|
Does this also clear the domainmetadata-cache? |
Collaborator
Author
|
It should. Maybe having a test for it would be nice, but I'm not sure how to go about that. |
Collaborator
Author
|
Rebased this in the hope of getting an all green CI. |
Collaborator
Author
these don't seem to be introduced by my PR? |
Member
Looks like #13587 so a rebase should help. |
Collaborator
Author
|
rebases for everyone! err, for this branch! |
Member
This one is indeed flaky, restarted. |
Collaborator
Author
green \o/ |
So far we never flushed the DNSSEC caches, except when DELETEing a domain. However clearly some operations can affect the DNSSEC settings, and then the caches should go. Also do this for the flush API, to be consistent, and for users writing to the DNSSEC settings/data externally.
Collaborator
Author
|
I fixed the rebase and this has also resulted in #13641 |
Habbie
approved these changes
Dec 18, 2023
This file contains hidden or 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
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.
Short description
So far we never flushed the DNSSEC caches, except when DELETEing a domain. However clearly some operations can affect the DNSSEC settings, and then the caches should go.
Also do this for the flush API, to be consistent, and for users writing to the DNSSEC settings/data externally.
Checklist
I have: