OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|6 days ago|
|cathead||3 years ago|
|tests||3 years ago|
|.gitignore||4 years ago|
|.gitreview||6 days ago|
|.test.conf||4 years ago|
|.testr.conf||3 years ago|
|LICENSE.txt||4 years ago|
|README.rst||3 years ago|
|example_config.py||3 years ago|
|requirements.txt||4 years ago|
|setup.cfg||4 years ago|
|setup.py||4 years ago|
|test-requirements.txt||4 years ago|
|tox.ini||4 years ago|
Cathead is a utility to monitor SSL certificates for expiry and retrieve new certificates when expiry is near.
This project is borne out of frustration with using cron and certmonger and various other bits of bash to monitor and renew certificates.
This project is under active development so expect changes to APIs and configurations.
Clone repo :
git clone https://github.com/takac/cathead
Install requirements and cathead into a virtual env. :
virtualenv .venv source .venv/bin/activate pip install -r requirements.txt pip install .
Construct a config file specifying which certs to track and how to refresh them. See the example_config.py file.
The certs section contains the details of the certificates to monitor and which driver should be used. The common name and other cert details should also be specified here.
Name of the driver to use. Use the name value from the driver.
Path to the key. This key will be regenerated at every refresh.
Path to the cert.
Common name of the certificate.
Callback action to execute on successful refresh of cert. Use the name value of an action defined in the actions section.
Callback action to execute on failure to refresh the cert. Use the name value of an action defined in the actions section.
The drivers section specifies how new certs are obtained, the only 2 drivers currently supported are Anchor (currently named ECA, due to be changed), and self signed certs.
Name of the driver used to associate with certificates.
Python class of the driver. e.g.
All other keys in the driver are passed into the driver class at construction. e.g.
The actions section contains actions to perform on different events. So far the possible events are
Actions can either by system calls or python calls.
Name of the action, used to associate with a certificate event callback.
The type of action, either
'system' for a system call (e.g.
'python' which allows executing a python callable.
Use this when using type of
python to select which module the callable is in.
Specify the command or callable to be run.
Specify the arguments to the command or callable. This should be a list.
Run cathead with your requirements file. :
For the self signing driver you will need to generate a key to sign the certs with. This can be done using :
openssl genrsa 2048 > ca.key
Known Issues """""""""""
Ctrl-C doesn't work
Currently you cannot interrupt the cathead process due running the process from the APScheduler thread. When you run
cathead config.pyin the terminal you have to terminate the process with