Common roles and playbooks for infrastructure deployment and management
  • Python 77.4%
  • Shell 19.2%
  • Jinja 3.4%
Find a file
irl 7fb23f3287
Some checks failed
Ansible Lint Check / lint (push) Failing after 59s
feat: remove podman_curl and point at sr2c.podman
2026-11-14 20:46:28 +00:00
.forgejo/workflows chore(deps): update actions/setup-python digest to 6d4fd22 2026-11-05 15:52:52 +00:00
meta feat: remove podman_curl and point at sr2c.podman 2026-11-14 20:46:28 +00:00
playbooks fix(lockdown): become: true 2026-10-31 21:36:00 +00:00
plugins/modules feat: remove podman_curl and point at sr2c.podman 2026-11-14 20:46:28 +00:00
roles feat: moves podman roles to podman collection 2026-11-14 20:34:25 +00:00
.ansible-lint.yml lint: ansible-lint suggested updates 2025-11-01 15:21:36 +00:00
.gitignore lint: ansible-lint suggested updates 2025-11-01 15:21:36 +00:00
galaxy.yml feat: moves podman roles to podman collection 2026-11-14 20:34:25 +00:00
README.md docs: we use upstream ansible lockdown now 2026-11-14 20:37:24 +00:00
renovate.json feat(podman_nginx): manage nginx and certbot with renovate 2026-11-12 17:51:43 +00:00

sr2.core

Usage

It is not possible for collections to depend on roles, so the roles must be included in your requirements.

collections:
  - src: git+https://guardianproject.dev/sr2/ansible-collection-core.git
    version: "main"
  - src: git+https://guardianproject.dev/sr2/ansible-collection-podman.git
    version: "main"
roles:
  - src: git+https://github.com/ansible-lockdown/RHEL9-CIS.git
    version: "2.4.2"

Convention

We assume that these roles will be run initially as root, and then as an unprivileged user after initial bootstrap. Some hardening may only be performed in the second run when we can see that the unprivileged user access is configured and root access is no longer required. If anything fails due to permissions when running as an unprivileged user, please report that in our issue tracker.

Licence

Copyright © SR2 Communications Limited 2021-2025.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.