Encapsulate rabbitmq credentials and Celery object connection into shared module
Following up #11 (closed), we need to extract the Celery connecting and credential-loading pieces replicated in the signing worker and "client" scripts, into some kind of shared module that we can easily (and securely) reuse.
It seems likely the credential-loading piece will need to be flexible to accommodate whatever the scenario is (likely environment variables) in production deployments, but also readily available to our localdev and CI environments (quite possibly .env
style setup in those two places would be feasible).
Edited by Christopher Gervais