b3ce43a596 set no_log on every task of two included files, which
test_include_uniform_apply_keyword rejects: a keyword every included task
repeats belongs in the include's apply block. The Cloudflare development
mode tasks and the ChatGPT bridge token tasks now receive no_log through
apply at their include sites. The matrix include had set no_log on the
include task itself, which never reaches the included tasks.
Two loops over MATRIX_BRIDGES were unmasked: the bridge folder creation
and the readiness gate. A loop result prints the whole item, and every item
carries the bridge's database_password, so both printed it at -v whenever
MASK_CREDENTIALS_IN_LOGS is on. The credential lint cannot see this because
the loop variable's name carries no secret marker.
Verified: test_include_uniform_apply_keyword, the credential masking lint,
the task lints and the matrix unit tests pass, and ansible-lint is clean on
the five files.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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-certif needed)
This role is intentionally small and reusable. It prepares the ground so app roles can just render their vHost.
Overview
This role front bootstrap for web apps: HTTPS base, optional Cloudflare setup, and handler wiring.
Cosmos
The diagram places Front Base (HTTPS + Cloudflare + Handlers) in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).
flowchart LR
subgraph role [sys-stk-front-base 💻]
svc_front_base["front-base"]
end
Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role's deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.
Features
- Automated provisioning: Configured by Ansible without manual steps.
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
domainto be provided by the consumer
Outputs
- Handler wiring completed
- HTTPS base ready (NGINX, ACME webroot)
- Cloudflare prepared (optional)
Credits
Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).