NetAuto Academy

Professional

Production Automation

The bridge from an already-reviewed change to a safe production rollout -- staging blast radius with nr.filter(), a real threshold gate that decides expand or abort, and automatic rollback when a stage fails.

A change can already be validated with dry-run and reviewed with a real Git diff, and still go wrong the moment it reaches a live fleet. This module is about that specific gap: what happens while a change rolls out, incrementally, to production. You'll use nr.filter() in a new role -- splitting a fleet into a small canary subset and everyone else -- then build a real stage-gate decision with run_stage() and evaluate_gate() that decides whether to expand or abort, verified on both a passing and a failing canary. You'll also wire NAPALM's rollback() to trigger automatically when a gate fails, rather than as a manual step.

Next up

Why Production Rollout Needs More Than Dry-Run and Review

0 / 5 complete

Lessons

  1. 1

    Why Production Rollout Needs More Than Dry-Run and Review

    A change has already been validated (dry-run, pre/post-check) and reviewed (a real Git diff, approved and merged). This lesson names the one thing nothing in this curriculum has taught yet: what happens while that change goes out to a real fleet, incrementally.

    Advanced11 min readNext up
  2. 2

    Staging the Blast Radius: nr.filter() as a Canary Gate

    nr.filter(), already fully taught in Phase 3.4, verified for real here in a new role: splitting a fleet into a small canary subset and everyone else, before any change goes out.

    Advanced11 min read
  3. 3

    Stage Gates: Validate, Then Expand — or Abort

    The module's one genuinely new mechanism: run_stage() and evaluate_gate(), verified for real on BOTH outcomes -- a canary that passes and one that fails -- not just the success path.

    Advanced14 min read
  4. 4

    Safe Rollback When a Stage Fails

    When Lesson 3's gate returns FAIL, this lesson connects that decision to a real, automatic rollback -- using NAPALM's already-known rollback(), triggered by code, not a manual step.

    Advanced12 min read
  5. 5

    Capstone: A Staged, Gated Production Rollout

    Every piece of this module -- canary selection, apply-then-validate staging, a threshold gate, and automatic rollback -- combined into one real, runnable script, executed on BOTH outcomes: a canary that passes and expands, and one that fails and rolls back.

    Advanced17 min read

Practice this module

Apply what you just covered -- hands-on practice and a knowledge check for this module.