You've already forked ansible-role-customca
41 lines
985 B
Markdown
41 lines
985 B
Markdown
|
ansible-role-customca
|
||
|
|
=========
|
||
|
|
|
||
|
|
This role exists to ensure that internal trusted ca's are added onto Linux hosts (RHEL 6,7 and 8).
|
||
|
|
|
||
|
|
Requirements
|
||
|
|
------------
|
||
|
|
|
||
|
|
The only requirements for this role to function are a CheckMK Enterprise instance. Configured with a baked updating agent.
|
||
|
|
The only requirements for using this role is a folder at your playbook root (files/ca_certs).
|
||
|
|
|
||
|
|
This folder should contain certs you wish to add to the trust store one per file.
|
||
|
|
|
||
|
|
files/ca_certs/
|
||
|
|
├── SOME_ISSUING_CA.crt
|
||
|
|
└── SOME-OFFLINE-ROOT-CA.crt
|
||
|
|
|
||
|
|
Role Variables
|
||
|
|
--------------
|
||
|
|
|
||
|
|
There are no Role Variables. Just relies on the folder structure outlined above
|
||
|
|
|
||
|
|
Dependencies
|
||
|
|
------------
|
||
|
|
|
||
|
|
This role is not dependant on any other.
|
||
|
|
|
||
|
|
Example Playbook
|
||
|
|
----------------
|
||
|
|
|
||
|
|
Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
|
||
|
|
|
||
|
|
- hosts: servers
|
||
|
|
roles:
|
||
|
|
- customca
|
||
|
|
|
||
|
|
License
|
||
|
|
-------
|
||
|
|
|
||
|
|
MIT
|