Configuration as Code for Ansible Automation Platform 2 Technical Workshop
IMPORTANT TO NOTE
This is the 4 hour workshop.
Welcome to our interactive lab on using Configuration as code to configure the Ansible Automation Platform.
Configuration as Code (CasC) is a software development practice that treats infrastructure configurations as code. This approach allows you to version control, track changes, and automate the deployment of your infrastructure configurations. With CasC, your configuration files or scripts serve as the single source of truth for your infrastructure setup. Any changes should be made through this mechanism, avoiding direct changes in the Ansible Automation Platform (AAP) UI.
Benefits of CasC include version control, consistency across environments, repeatability, automated deployment, and auditing and compliance.
Workshop Resources
| Resource | Link |
|---|---|
| Workshop content and exercises | Config as code Introduction to AAP (RHDP) |
| Follow-up assets | Infra Collections in Ansible Galaxy |
| Presenter instructions and guide | Introduction to automation controller (prerequisite lab) |
Who is this workshop best for?
This workshop is for Ansible automation engineers who want to manage Ansible Automation Platform configuration using Configuration as Code practices.
Target audience
Ansible automation engineers, platform administrators, and DevOps engineers responsible for maintaining Ansible Automation Platform.
Attendee Prerequisites
- Familiarity with Ansible Automation Platform and automation controller
- Recommended: complete the Introduction to automation controller lab first
Presentation Deck
Presentation materials are included in the lab environment. Refer to the Config as code Introduction to AAP lab for the latest deck.
Lab provisioner
This lab is available via the Red Hat Demo Platform. This is a Red Hat or Partner Only Lab — please reach out to your account representative to coordinate access.
Lab Index (Estimate total time ⏱️ 4 hours)
In this lab, we will demonstrate how to use Configuration as Code to configure various aspects of the Ansible Automation Platform (AAP):
- Setting up the basics for configuring the Automation Platform
- Creating credentials, inventories, and job templates
- Configuring the Hub to load in more content
- Building an execution environment to be used on the platform
- Creating a workflow from scratch (extra credit)
| Activity | Link | Estimated Time |
|---|---|---|
| Part 1: Creating the Basics for configuring the Automation Platform | 🚀 Launch Lab | ⏱️ 40 minutes |
| Part 2: Creating credentials, inventories, and job templates | ⏱️ 40 minutes | |
| Part 3: Configuring the Automation hub to load more content | ⏱️ 30 minutes | |
| Part 4: Build an execution environment to be used on the platform | ⏱️ 40 minutes | |
| Part 5: Creating an Automation controller Workflow in code | ⏱️ 90 minutes |
Going Further
Additional material for Configuration as Code for Ansible Automation Platform 2
| Title | Type | Link |
|---|---|---|
| Demystifying Ansible Automation Platform | Book | 📖 Demystifying Ansible Automation Platform - Book from Packt |
| Infra Collections in Ansible Galaxy | Collections | 📒 Download collections used in this lab and get links to their repos |
Ansible Workshop
This is an official Ansible Workshop
This workshop is maintained by the Infra Config as Code Volunteers Please open an issues on Github
