Files
computer-playbook/roles/sys-stk-front-base
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
..

Front Base (HTTPS + Cloudflare + Handlers) 🚀

Description

sys-stk-front-base bootstraps the front layer that most web-facing apps need:

  • Ensures the HTTPS base via sys-svc-webserver-https
  • (Optional) Cloudflare bootstrap (zone lookup, dev mode, purge)
  • Wires OpenResty/Nginx handlers
  • Leaves per-domain certificate issuance to consumer roles (or pass-through vars to sys-util-csp-cert if needed)

This role is intentionally small and reusable. It prepares the ground so app roles can just render their vHost.

Responsibilities

  • Include sys-svc-webserver-https (once per host)
  • Include Cloudflare tasks when DNS_PROVIDER == "cloudflare"
  • Load handler utilities (e.g., svc-prx-openresty)
  • Stay domain-agnostic: expect domain to be provided by the consumer

Outputs

  • Handler wiring completed
  • HTTPS base ready (Nginx, ACME webroot)
  • Cloudflare prepared (optional)