Network Automation
Intent Pipelines with Git-Backed Templates
Wire a small Git flow that renders configs, runs policy checks, and posts diffs humans actually read.
Tuition (informational)
540,000 KRW
No checkout on this site—coordinators confirm scope before invoices.
Hybrid studio blocks
3 sessions · 12 lab hours
Scenario brief
Automation without guardrails is just faster mistakes. You stand up a pipeline that ingests YAML intent, renders vendor configs, and blocks merges when descriptions are missing. The lab nudges you toward readable diffs and kinder on-call pages.
Lead mentor
Noah Im
Writes curriculum like release notes: terse, kind, and dated.
Inside the lab
- Sample repo with branch protections enabled
- Static checks that fail on vague commit messages
- Render previews side-by-side with live device state
- Mentor session on writing operator-friendly rollback tickets
- Integration stub for ticketing without storing secrets
- Activity log export for auditors who ask polite but firm questions
- Capstone: ship a change bundle your peer can deploy blindfolded
Outcomes
- Treat automation as a collaboration surface, not a solo script
- Catch risky drift before it reaches maintenance windows
- Document intent so new hires do not fear the repo
Logistics questions
Cohort notes
“Intent Pipelines with Git-Backed Templates made our diffs boring in the best way. Boring means predictable.”
Theo · Harborline Transit IT
Via survey
“I wanted more time on secret rotation patterns, but the merge gate exercises alone were worth the enrollment.”
Rina · SRE