feat: add debug CRL refresh controls [WPB-24945]#4839
Conversation
be7e43a to
f19cb1b
Compare
|
|
@Garzas looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #4839 +/- ##
===========================================
+ Coverage 51.26% 51.29% +0.02%
===========================================
Files 611 611
Lines 21181 21201 +20
Branches 3405 3407 +2
===========================================
+ Hits 10859 10875 +16
- Misses 9308 9310 +2
- Partials 1014 1016 +2
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|



https://wearezeta.atlassian.net/browse/WPB-24945
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764The PR Description
What's new in this PR?
Issues
Adds a private debug setting for testing E2EI CRL revocation updates faster than the normal CRL expiry cycle.
QA needs a way to force CRLs to expire quickly so revoked certificates can be detected without waiting up to 24 hours.
Causes (Optional)
The existing CRL revocation check button could trigger a manual check, but there was no working debug control that kept CRL expiry short for repeated testing.
Solutions
Adds a
Force CRL expiry after 1 minuteswitch in private debug tools.When enabled, the app:
When disabled, the app stops using the debug expiry behavior and returns to the normal CRL expiry flow.