Skip to content

docs: update terminology from Zero Trust to Private Mesh across vario… - #32

Merged
Miguel-DevOps merged 1 commit into
mainfrom
chore/private-mesh-wording-in-code
Nov 16, 2026
Merged

Miguel-DevOps merged 1 commit into
mainfrom
chore/private-mesh-wording-in-code

Conversation

@Miguel-DevOps

Copy link
Copy Markdown
Contributor

This pull request updates terminology across the codebase to consistently use "Private Mesh" instead of "Zero Trust" when referring to the network architecture and related policies. This change improves clarity and aligns the documentation and code comments with the current naming conventions. The updates span Makefiles, Ansible playbooks, roles, and configuration templates.

Terminology update: "Zero Trust" → "Private Mesh"

  • Makefile and playbooks:

    • Changed echo statements and documentation in Makefile and various playbooks to replace "Zero Trust" with "Private Mesh" in descriptions of network policies and overlays. [1] [2] [3] [4] [5] [6]
  • Security and firewall configuration:

    • Updated comments and failure messages in nftables_rules.yml to refer to "Private Mesh" instead of "Zero Trust" when describing control-plane port restrictions. [1] [2]
  • Tailscale and ACLs:

    • Modified task names and assertions in Tailscale-related Ansible roles to reflect the new terminology.
  • Application configuration:

    • Updated the Caddyfile template to use "Private Mesh VPN restriction" in section headers.

@Miguel-DevOps
Miguel-DevOps merged commit eef7deb into main Nov 16, 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