All modules
Module 7·Course coverage: 10%

Automating the Network

APIs and data formats, controllers, configuration as code, AI in operations, change pipelines, and YANG device APIs.

Modern networks expose configuration and state through APIs, not just the CLI. Start with why hand-typed change breaks at scale, learn the REST APIs and data formats (JSON, YAML) every tool is built on, see how controllers and SDN use them, meet the tools that turn configuration into code and where AI fits in day-to-day operations, then finish with a source of truth that every change flows through in a reviewed pipeline, and the data models and device APIs underneath it all: YANG, NETCONF, RESTCONF and XML.

7 chapters3h study timeCourse coverage: 10%Course plan
Forgy· module 7 intro

Welcome to module 7. APIs and data formats, controllers, configuration as code, AI in operations, change pipelines, and YANG device APIs. I'll meet you again at the top of every chapter — this module's course coverage is 10%, so don't rush it. Pick chapter 7.1 below to start.

Course plan

Modules 2–8 are part of the Course & Lab Pass and All-Access Max — start with a free account

Anyone can browse the syllabus and preview every chapter. Modules 2–8 come with the Course & Lab Pass and All-Access Max. A free account opens Module 1: How Networks Work end-to-end and saves your labs — start there, no card required.

  • Read every chapter in Module 1 — How Networks Work
  • Save labs of up to 5 devices
  • Save up to 3 topologies
  • See the full course syllabus + chapter titles

Free account · no card required · compare plans any time

  1. 7.1

    Why automate networks?

    Manual CLI doesn't scale. Network automation reduces error, accelerates change, and enables consistency at scale. This chapter introduces the why and the high-level patterns: configuration management, intent-based, GitOps.

    Beginner·25 min·4 quiz Q
  2. 7.2

    REST APIs, JSON, and YAML

    Modern network devices expose REST APIs returning JSON. Configuration as code lives in YAML files. This chapter teaches the bare minimum to read and write both, plus a worked REST GET against a NetForge-like device.

    Intermediate·35 min·4 quiz Q
  3. 7.3

    Controllers, SDN, and intent-based networking

    Software-Defined Networking separates the control plane from the data plane and exposes a centralized API. This chapter explains controllers, southbound vs northbound APIs, and intent-based software-defined fabrics.

    Advanced·25 min·4 quiz Q
  4. 7.4

    Configuration as code — push, pull and plan

    Each of the major configuration tools has a different philosophy: agentless vs agented, push vs pull, declarative vs imperative. You should be able to recognize each.

    Intermediate·30 min·4 quiz Q
  5. 7.5

    AI on the operations desk — prediction and assistants

    AI and ML are now core to modern network operations. This chapter explains the difference between generative and predictive AI, where each shows up in netops today (assistants, anomaly detection, capacity forecasting, ChatOps), and the limits you need to understand.

    Intermediate·25 min·4 quiz Q
  6. 7.6

    Source of truth and change pipelines

    Automation is only as good as the data it pushes. This chapter covers where a network's intended state lives (the source of truth), the Git workflow engineers use to change it, the pipeline that reviews, tests, deploys, verifies and rolls back every change, and how drift between the source of truth and the running devices is found and handled.

    Advanced·20 min·4 quiz Q
  7. 7.7

    Data models and device APIs: YANG, NETCONF, RESTCONF and XML

    Scripts that scrape CLI text break whenever the text changes. This chapter shows what replaces it: YANG data models, NETCONF and its candidate datastore, RESTCONF URLs and media types, the same interface written in XML and in JSON, streaming telemetry, and how the CLI, SNMP, NETCONF and RESTCONF compare.

    Advanced·20 min·4 quiz Q