JonasPammer’s Ansible roles

This page is being periodically re-generated by a GitHub Action.

Table of Contents

• Ansible Roles
  • Dependencies
    • Soft Dependencies
    • Hard Dependencies

Ansible Roles

ℹ️	1 Issue is always open for the Renovate Dependency Dashboard!

Role name (hover badge for description)	Action Status	Version	Open Issues *Note	Open Pull Requests
🍪 cookiecutter-ansible-role
bootstrap
core_dependencies
pip
shellcheck
motd
apache2
openssl
goaccess
mediawiki
gitlab

Dependencies

Soft Dependencies

Most roles have a set of “soft dependencies” described in their requirements.yml file. These soft dependencies are used in the relevant CI Tests to prepare the machine for the execution of a given role or to test some kind of interoperability.

You can choose to use those roles if you like them.

Here is an overview of all roles with their soft dependencies:

The dependencies are soft for these reasons:

• Better re-usability.

• Easier to fork.

• Lets the system developer assume a start-state of a machine.

Because these dependencies are loose, you have to include them in your playbook yourself (assuming you want to use them):

- name: make the best machine ever
  hosts: all
  become: true

  roles:
    - name: jonaspammer.bootstrap
    - name: jonaspammer.java

Hard Dependencies

Some roles have a required hard dependency on another role, mainly for a common handler or for variables that are set in the parent role and used in the child role. These role dependencies (official documentation) are described in meta/main.yml file of a given role under dependencies.

Role name	Depends on	Reason

Here is an overview of all hard dependencies:

Because Ansible defines role dependencies as 'prerequisites' and not 'true dependencies', you still have to include them in your playbook yourself:

- name: Converge
  hosts: all
  become: true

  roles:
    # (preperation roles have been left out for this example)

    - name: jonaspammer.httpd
    - name: jonaspammer.php