It looks like it is going to be a couple more weeks before we get a fix for the LSBC issue about revocations. To deal with the issue over time, please do the following:
Beginning immediately -- periodically, at least each weekday, run the fixRevReg (false) to see if there is a difference and if so, run the fixRevReg (true) endpoint to fix it. If someone else can run that, (perhaps @swcurran -- let us know how).
Create a cron job that runs the fixRevReg (false) test every few minutes and sends a notification when a problem is detected.
If you are comfortable fully automating the process, have the cron job also run the fixRevReg (true) step
Recognize that the need for this will only be here for a few more weeks, so balance out the effort for automating this (including testing / risk mitigation) with the time will need to do this.
@ianco is working on better fixes to eliminate the tracking concern.
It looks like it is going to be a couple more weeks before we get a fix for the LSBC issue about revocations. To deal with the issue over time, please do the following:
fixRevReg (false)
to see if there is a difference and if so, run thefixRevReg (true)
endpoint to fix it. If someone else can run that, (perhaps @swcurran -- let us know how).fixRevReg (false)
test every few minutes and sends a notification when a problem is detected.fixRevReg (true)
stepRecognize that the need for this will only be here for a few more weeks, so balance out the effort for automating this (including testing / risk mitigation) with the time will need to do this.
@ianco is working on better fixes to eliminate the tracking concern.