Skip to content

Refactor/ingress sops decoupling and toolchain gates - #23

Merged
Miguel-DevOps merged 9 commits into
mainfrom
refactor/ingress-sops-decoupling-and-toolchain-gates
Nov 1, 2026
Merged

Miguel-DevOps merged 9 commits into
mainfrom
refactor/ingress-sops-decoupling-and-toolchain-gates

Conversation

@Miguel-DevOps

Copy link
Copy Markdown
Contributor

This pull request introduces several important improvements to the project's infrastructure, focusing on standardizing developer workflows, enhancing security and privacy, and updating documentation and dependencies. The most significant changes are the decoupling of ingress routing configuration from secrets, the introduction of a deterministic Makefile toolchain contract, and an upgrade to the Caddy WAF image with cryptographic validation. Documentation has also been updated to clarify operational boundaries and best practices.

Developer Tooling & Workflow Standardization:

  • Added standard Makefile targets (tools, doctor, test-security, release-ready) to unify developer and automation entrypoints, including diagnostics and security auditing. [1] [2] [3]

Ingress & Secrets Decoupling:

  • Decoupled ingress_services and ingress_security_profiles from SOPS-encrypted secrets: these are now tracked in plain YAML (ingress.yml.example and ingress.yml), improving privacy and reducing merge conflicts. Documentation and inventory files were updated to reflect this separation, and references to the .example.j2 template were removed in favor of a single Caddyfile.j2 SSOT. [1] [2] [3] [4] [5] [6] [7] [8]

Security & Compliance Improvements:

  • Upgraded the Caddy WAF image to v3.6.2 (Coraza v3.8.1, CRS v4) and updated its cryptographic digest for supply chain verification. [1] [2]
  • Hardened the audit log file permissions from 0644 to 0640 for improved security.

Documentation & Operational Guidance:

  • Documented operational scale and sizing boundaries for bare metal/VPS deployments, including recommended node counts and architectural roles, and clarified the repository's position as a foundation for future orchestration. [1] [2]
  • Updated the roadmap to use uv tool run instead of pip for toolchain compliance. [1] [2]
  • Added clarifying comments and improved error messages for preflight and validation steps. [1] [2] [3]

These changes collectively improve the maintainability, security, and scalability of the project while making developer onboarding and operational procedures more robust and transparent.

…ngress vars

    - Move ingress_services and ingress_security_profiles out of secrets.sops.yml.example
    - Provide neutral RFC 2606 templates in inventory/group_vars/all/ingress.yml.example
    - Add inventory/group_vars/all/ingress.yml to .gitignore to prevent client domain leakage
    - Define baseline ingress_security_profiles in inventory/group_vars/all/main.yml
…copy requirement

    - Promote Caddyfile.example.j2 to tracked SSOT template roles/L4_networking/caddy/templates/Caddyfile.j2
    - Add global metrics directive aligned with upstream Developmi/caddy-waf
    - Update .dockerignore to align template exclusion patterns
…assertions

    - Remove controller-side Caddyfile.j2 existence check in playbooks/l4/edge.yml
    - Update preflight error message in roles/L4_networking/caddy/tasks/main.yml pointing to ingress.yml.example
…0640 audit log mode

    - Render Caddyfile.j2 instead of obsolete example template in converge.yml
    - Update audit log mode assertion from 0644 to 0640 in verify.yml to match hardened task defaults
…l positioning

    - Document node sizing thresholds (1-5 Brain nodes, 50-100 Muscle workers)
    - Clarify Phase 1 bare metal and VPS hardening baseline prior to hyperscale K8s orchestration
    - Clarify configuration topology boundary between host variables and non-secret ingress catalog
    - Update caddy_image pin to ghcr.io/developmi/caddy-waf:v3.6.2
    - Update multi-arch OCI index sha256 digest to sha256:572968506168150bed96e293c9461578d911a980ecb8ef91d6672f381dda2cbb
…ose entrypoint

    - Replace pip install graphifyy with uv tool run in docs/project/ROADMAP.md
    - Document official upstream container entrypoint requirement for yarn in apps/twenty-crm/docker-compose.yml
…y targets

    - Add make tools target aliased to local toolchain setup
    - Add make doctor target for diagnostic environment and playbook readiness verification
    - Add make test-security target combining pip-audit and zizmor workflow scanning
    - Add make release-ready comprehensive verification gate
… gates

    - Add [Unreleased] section detailing Make targets, sizing boundaries, and ingress decoupling
@Miguel-DevOps
Miguel-DevOps merged commit 59501f5 into main Nov 1, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant