mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2025-12-08 10:26:35 +00:00

Files

Kevin Veen-Birkenbach 716ebef33b Refactor task includes and update variable handling for Ansible 2.20 migration

This commit updates multiple roles to ensure compatibility with Ansible 2.20.
Several include paths and task-loading mechanisms required adjustments,
as Ansible 2.20 applies stricter evaluation rules for complex Jinja expressions
and no longer resolves certain relative include paths the way Ansible 2.18 did.

Key changes:
- Replaced legacy once_finalize.yml and once_flag.yml with the new structure
  under tasks/utils/once/finalize.yml and tasks/utils/once/flag.yml.
- Updated all include_tasks statements to use 'path_join' with playbook_dir,
  ensuring deterministic and absolute file resolution across roles.
- Fixed all network helper includes by converting direct relative paths such as
  'roles/docker-compose/tasks/utils/network.yml' to proper Jinja-evaluated paths.
- Normalized MATOMO_* variable names for consistency with the updated variable
  scope behavior in Ansible 2.20.
- Removed deprecated patterns that were implicitly supported in Ansible 2.18
  but break under the more strict variable and path resolution model in 2.20.

These changes are part of the full migration step required to ensure the
infinito-nexus roles remain stable, deterministic, and forward-compatible with
Ansible 2.20.

Details of the discussion and reasoning can be found in this conversation:
https://chatgpt.com/share/69300a8d-24d4-800f-bec0-e895a695618a

2025-12-03 11:02:34 +01:00

config

CSP (Safari-safe): merge -elem/-attr into base; respect explicit disables; no mirror-back; header only for documents/workers

2025-10-22 13:53:06 +02:00

README.md

Jira

Description

Jira Software is Atlassian’s issue and project-tracking platform. This role deploys Jira via Docker Compose, connects it to PostgreSQL, and adds proxy awareness, optional OIDC SSO, health checks, and production-oriented defaults for Infinito.Nexus.

Overview

The role builds a lean custom image on top of the official Jira Software image, provisions persistent volumes, and exposes the app behind your reverse proxy. Variables control image/version/volumes/domains/SSO. JVM heap sizing is auto-derived from host RAM with safe caps to prevent Xms > Xmx.

Features

Fully Dockerized: Compose stack with a dedicated data volume (jira_data) and a minimal overlay image to enable future plugins/config.
Reverse-Proxy/HTTPS Ready: Preconfigured Atlassian Tomcat proxy envs so Jira respects external scheme/host/port.
OIDC SSO (Optional): Pre-templated vars for issuer, client, endpoints, scopes; compatible with Atlassian DC SSO/OIDC marketplace apps.
Central Database: PostgreSQL integration (local or central) with credentials sourced from role configuration.
JVM Auto-Tuning: Safe calculation of JVM_MINIMUM_MEMORY / JVM_MAXIMUM_MEMORY with caps to avoid VM init errors.
Health Checks: Container healthcheck for quicker failure detection and stable automation.
CSP & Canonical Domains: Integrates with platform CSP and domain management.
Backup Ready: Persistent data under {{ JIRA_STORAGE_PATH }}.

Further Resources

Product page: Atlassian Jira Software
Docker Hub (official image): atlassian/jira-software