16 Added mow to pacer_to_cl_ids and implemented a logger to detect similar issues #17
Conversation
albertisfu
force-pushed
the
16-add-mow-to-pacer-to-cl-ids-and-log-similar-issues
branch
from
ceed601 to
6195a5a
Compare
albertisfu
force-pushed
the
16-add-mow-to-pacer-to-cl-ids-and-log-similar-issues
branch
from
6195a5a to
357862e
Compare
mlissner
deleted the
16-add-mow-to-pacer-to-cl-ids-and-log-similar-issues
branch
|
It doesn't look like we have automated deployment for this, do we? I totally forget, but I'm not seeing it in the Github Actions. |
|
no, we deployed it manually. I'll take care of this unless I run into permission issues, in which case I'll ask for help |
|
Ok, this is already deployed! I'm not sure if updating the runtime in the template to 3.11 caused the environment variables to be cleared during the deployment process. However, after the deployment, I found that they were not set. So, I immediately set them again via the console. That caused 4 recap-email requests to return an invalid token from CL. To fix it I created the EPQs using the admin panel and processed them manually, so this is resolved. Next time we deploy this, I'll review the environment variables being set. They probably need to be passed during deployment. |
This PR resolves #16 by adding
mow->mowdto thepacer_to_cl_idsmapping.Additionally, a method was added to send similar issues to Sentry. If an email is received indicating that CL returns an invalid court PK error, the issue is reported so we can take action and fix the problem by adding the required court mapping.
New related tests have been added for these changes.
The CI actions have also been updated, as they were no longer compatible with the GitHub environment.
Additionally, related lint complaints were fixed to ensure they pass.