-
Notifications
You must be signed in to change notification settings - Fork 923
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
auth api: flush all caches when flushing #13514
Conversation
Pull Request Test Coverage Report for Build 7226248045
💛 - Coveralls |
Does this also clear the domainmetadata-cache? |
It should. Maybe having a test for it would be nice, but I'm not sure how to go about that. |
Rebased this in the hope of getting an all green CI. |
these don't seem to be introduced by my PR? |
Looks like #13587 so a rebase should help. |
rebases for everyone! err, for this branch! |
This one is indeed flaky, restarted. |
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.
I fixed the rebase and this has also resulted in #13641 |
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: