From 5a8be80f4365c908a34a2d1133e3015282e16e1d Mon Sep 17 00:00:00 2001 From: medusa Date: Tue, 5 Aug 2025 23:39:33 -0500 Subject: [PATCH] Update tech_docs/Jinja2_guide.md --- tech_docs/Jinja2_guide.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tech_docs/Jinja2_guide.md b/tech_docs/Jinja2_guide.md index 9557e5f..86e2a60 100644 --- a/tech_docs/Jinja2_guide.md +++ b/tech_docs/Jinja2_guide.md @@ -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). If you only have 15 min right now, jump to the “Tonight” section at the end. +```plaintext ──────────────────────────────────────────────────────── 1. YAML → Jinja2 → Device in <10 s ──────────────────────────────────────────────────────── @@ -164,7 +165,7 @@ Encrypt: sops -e vars/secrets.yml Diff: colordiff -u live.cfg new.cfg Copy the snippets above into your repo and you’re 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. Let’s sharpen it further with battle-tested patterns and CLI-ready examples. Here’s your playbook: