Update tech_docs/Jinja2_guide.md

This commit is contained in:
2025-08-05 23:39:33 -05:00
parent 8a5f28e3bb
commit 5a8be80f43

View File

@@ -3,6 +3,7 @@ It is organized by *pain points* I see teams hit once they move past the first 5
Everything is copy-paste ready (CLI one-liners, tiny Python/Go helpers, Ansible snippets). Everything is copy-paste ready (CLI one-liners, tiny Python/Go helpers, Ansible snippets).
If you only have 15 min right now, jump to the “Tonight” section at the end. If you only have 15 min right now, jump to the “Tonight” section at the end.
```plaintext
──────────────────────────────────────────────────────── ────────────────────────────────────────────────────────
1. YAML → Jinja2 → Device in <10 s 1. YAML → Jinja2 → Device in <10 s
──────────────────────────────────────────────────────── ────────────────────────────────────────────────────────
@@ -164,7 +165,7 @@ Encrypt: sops -e vars/secrets.yml
Diff: colordiff -u live.cfg new.cfg Diff: colordiff -u live.cfg new.cfg
Copy the snippets above into your repo and youre already ahead of most teams. Copy the snippets above into your repo and youre already ahead of most teams.
```
--- ---
This is **exactly** the kind of tactical, network-focused Jinja2 guide I wish I had when I started automating configs. Lets sharpen it further with battle-tested patterns and CLI-ready examples. Heres your playbook: This is **exactly** the kind of tactical, network-focused Jinja2 guide I wish I had when I started automating configs. Lets sharpen it further with battle-tested patterns and CLI-ready examples. Heres your playbook: