Learning paths › Automation › Vault, variables and config changes
Vault, variables and config changes
Where a playbook's values come from and what its changes actually do: the vault password supplied without retyping, variables shared across a group or given to one device, structured facts gathered from an IOS device and printed, a show command waited on for a condition and a prompt answered — then configuration, backed up and diffed before it lands, a line placed inside the right block several levels deep, config lines moved out of the playbook into a file, match strictness and single-line against whole-block replacement, and the resource modules that manage hostname, interface attributes, addressing, VLANs, local accounts and per-VRF static routes as structured data. Explanation and checks; five written exercises.
Lessons
- Supply the vault password without retyping it
- Share values across an inventory group
- Give one device its own variables
- Gather structured facts from an IOS device
- Print a variable to see what you have
- Run show commands and wait for a condition
- Answer a command that asks a question
- Back up the running config before you change it
- Choose what the diff compares against
- Place a line inside the right config block
- Reach a block several levels deep
- Move config lines out of the playbook into a file
- Decide when to write config to startup
- Clear an access list before rewriting its rules
- Append commands once a change is applied
- Control how strictly lines are compared
- Send one differing line or the whole block
- Manage a feature as structured data
- Set a hostname and read the before/after result
- Own description, speed and MTU per interface
- Assign IPv4 and IPv6 addresses declaratively
- Set access VLANs and trunks declaratively
- Manage local device accounts
- Declare static routes per VRF and family
More in Automation
- First scripts that configure devices
- NAPALM: structured data across vendors
- Concurrency, and the Python types device output returns
- Parsing show output and testing conditions
- Readable code, branching and loops
- Build the workstation and the toolchain
- Files, CSV, JSON and pickle
- Paramiko: SSH to devices from Python
- Netmiko at fleet scale
- Tuples, sets and dictionaries for device records
- Exceptions and your first classes
- Plan and build the automation lab
- Files, formatting and regular expressions
- Addresses, functions, modules and classes
- CSV inventories, logging and scheduling
- Netmiko, SCP and structured parsing
- Agents, async and model-driven workflows
- NETCONF, YANG and RESTCONF
- NX-API, pyATS and Genie
- A small GenAI app, end to end
- macOS, Linux and the virtual lab
- Agile delivery and Python fundamentals
- REST APIs, authentication and requests
- Flask, Docker and Jenkins
- Managing a router with NETCONF and RESTCONF
- Ansible: inventory, ad-hoc commands and first playbooks
- Roles and zero-touch provisioning for Linux switches
- Installing the controller and applying a project
- Setting up Python 3
- The Ansible lab and the controller
- Parsing output and knowing which variable wins
- Jinja filters and PAN-OS automation
- Loops, callbacks, strategy and run control
- Roles, imports and writing your own module
- Running playbooks from AWX