Update tech_docs/Jinja2_guide.md
This commit is contained in:
@@ -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:
|
||||
|
||||
Reference in New Issue
Block a user