stephrobert.openscap
stephrobert.openscap
⭐ Star us on GitHub — it motivates us a lot!
Install Oscap
Platforms Supported:
| Platform | Versions |
|---|---|
| Debian | bullseye |
| Ubuntu | jammy |
⚠️ Requirements
Ansible >= 2.11.
Ansible role dependencies
None.
⚡ Installation
Install with Ansible Galaxy
ansible-galaxy install stephrobert.openscap
Install with git
If you do not want a global installation, clone it into your roles_path.
git clone [email protected]:stephrobert/ansible-role-openscap.git stephrobert.openscap
But I often add it as a submodule in a given playbook_dir repository.
git submodule add [email protected]:stephrobert/ansible-role-openscap.git roles/stephrobert.openscap
As the role is not managed by Ansible Galaxy, you do not have to specify the github user account.
✏️ Example Playbook
Basic usage is:
- hosts: all
roles:
- role: stephrobert.openscap
vars:
content_version: 0.1.71
install_content: false
install_oscap: true
oscap_version: 1.3.9
reports_folder: /opt/openscap-reports
scan: false
⚙️ Role Variables
Variables are divided in three types.
The default vars section shows you which variables you may override in your ansible inventory. As a matter of fact, all variables should be defined there for explicitness, ease of documentation as well as overall role manageability.
The context variables are shown in section below hint you on how runtime context may affects role execution.
Default variables
Role default variables from defaults/main.yml.
| Variable Name | Value |
|---|---|
| install_content | False |
| install_oscap | True |
| oscap_version | 1.3.9 |
| content_version | 0.1.71 |
| scan | False |
| reports_folder | /opt/openscap-reports |
Context variables
Those variables from vars/*.{yml,json} are loaded dynamically during task
runtime using the include_vars module.
Variables loaded from vars/main.yml.
Author Information
none
ansible-galaxy install stephrobert.openscap