triplepoint.self_signed_certificates
Intro
This guide provides instructions on how to install and set up self-signed certificates for several domains.
There's a variable called certbot_certs
that isn't specific to this role. It is designed to mimic the geerlingguy.certbot
role, allowing for easy substitution during testing. For more details, check the role variables.
Requirements
None.
Role Variables
Refer to the comment in the default variables file for configuration details.
Dependencies
None.
Example Playbook
- hosts: whatever
roles:
- triplepoint.self_signed_certificates
Role Testing
This role has been tested using molecule
, with pipenv
managing dependencies and the Python testing setup.
Setting Up Your Execution Environment
pip install pipenv
After installing pipenv
, create the execution virtual environment with:
pipenv install --dev
Running Tests
With your environment ready, run the tests with:
pipenv run molecule test
Regenerating the Lock File
You generally won't need to do this often, but if you change Python package requirements with pipenv install {some_package}
or by editing the Pipfile
, or if you notice that the build dependencies are outdated, you'll need to regenerate the Pipfile.lock
.
pipenv update --dev
Make sure to save the updated Pipfile.lock
after this process.
License
MIT
A generator for self-signed certificates with a local CA cert, intended to stand in for geerlingguy.certbot during testing or local deployments.
ansible-galaxy install triplepoint.self_signed_certificates