Skip to content

Commit 8b0dcd9

Browse files
IPvSeanIPvSean
committed
fix config as code
1 parent 0427052 commit 8b0dcd9

3 files changed

Lines changed: 40 additions & 163 deletions

File tree

‎README-WORKSHOPS.md‎

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -113,19 +113,6 @@
113113
Lab Page
114114
<svg width="25" height="16" viewBox="0 0 25 16" fill="none" xmlns="http://www.w3.org/2000/svg">
115115
<path fill-rule="evenodd" clip-rule="evenodd" d="M17.8631 0.929124L24.2271 7.29308C24.6176 7.68361 24.6176 8.31677 24.2271 8.7073L17.8631 15.0713C17.4726 15.4618 16.8394 15.4618 16.4489 15.0713C16.0584 14.6807 16.0584 14.0476 16.4489 13.657L21.1058 9.00019H0.47998V7.00019H21.1058L16.4489 2.34334C16.0584 1.95281 16.0584 1.31965 16.4489 0.929124C16.8394 0.538599 17.4726 0.538599 17.8631 0.929124Z" fill="#000000"/>
116-
</svg>
117-
</span>
118-
<div id="lab_powered_by"><img src="assets/images/instruqt-logo.svg"></div>
119-
</a>
120-
<!-- lab -->
121-
<a target="_new" href="exercises/instruqt/aapcasc" class="data-card">
122-
<h3>CaC</h3>
123-
<h4>CaC for Ansible Automation Platform</h4>
124-
<p>Focused on Configuration as Code for Ansible Automation Platform.</p>
125-
<span class="link-text">
126-
Lab Page
127-
<svg width="25" height="16" viewBox="0 0 25 16" fill="none" xmlns="http://www.w3.org/2000/svg">
128-
<path fill-rule="evenodd" clip-rule="evenodd" d="M17.8631 0.929124L24.2271 7.29308C24.6176 7.68361 24.6176 8.31677 24.2271 8.7073L17.8631 15.0713C17.4726 15.4618 16.8394 15.4618 16.4489 15.0713C16.0584 14.6807 16.0584 14.0476 16.4489 13.657L21.1058 9.00019H0.47998V7.00019H21.1058L16.4489 2.34334C16.0584 1.95281 16.0584 1.31965 16.4489 0.929124C16.8394 0.538599 17.4726 0.538599 17.8631 0.929124Z" fill="#000000"/>
129116
</svg>
130117
</span>
131118
<div id="lab_powered_by"><img src="assets/images/instruqt-logo.svg"></div>

‎exercises/instruqt/aapcasc-4.md‎

Lines changed: 40 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,40 @@
11
# Configuration as Code for Ansible Automation Platform 2 Technical Workshop
22

3-
> **IMPORTANT TO NOTE**
4-
>
5-
> This is the 4 hour version of this workshop. For the shorter 90 minute session please [🔬 click here](aapcasc.md)
3+
> **IMPORTANT TO NOTE**
4+
>
5+
> This is the 4 hour workshop.
66
>
77
88

99
Welcome to our interactive lab on using Configuration as code to configure the Ansible Automation Platrom.
1010

11-
Configuration as Code(CasC) is the way to maintain all your infrastructure.
11+
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.
12+
Benefits of CasC
13+
By adopting a Configuration as Code approach, you can enjoy numerous benefits, including:
14+
15+
* Version Control : Track changes and collaborate with team members.
16+
* Consistency : Ensure consistent configurations across different environments.
17+
* Repeatability : Repeat the same configuration setup multiple times.
18+
* Automated Deployment : Automate deployment to different environments.
19+
* Auditing and Compliance : Track who made changes, when, and what was changed.
20+
21+
== Lab structure
22+
23+
In this lab, we will demonstrate how to use Configuration as Code to configure various aspects of the Ansible Automation Platform (AAP). This includes:
24+
25+
* First, We will setup the basics for configuring the Automation Platform.
1226

13-
This lab will provide code to demonstrate how to use CasC to maintain all aspects of AAP. The provided code will be a starting point, and will guide the user through how to utilize the code, and make it their own. This lab will cover configuring controller, private automation hub, execution environments, as well as the creation of workflows without the GUI as an example to follow along. These principles will help to prevent drift in configuration, allow changes to require approval before implementation, and help to maintain both a development and prod deployment.
27+
* Next we will Create some credentials, inventories, and job templates and everything that is needed to create them.
1428

15-
It is Recomended to be familiar with the Automation Controller and Ansible as this lab assumes you are familier with using those products.
29+
* Next we will configure the Hub to load in more content.
1630

17-
If you have not used the Automation controller before, a recomended place to start is this instruct lab, if you have not done so before:
31+
* We will then build an execution environment to be used on the platform.
32+
33+
* Finally for extra credit, a workflow can be created from scratch.
34+
35+
By following this lab, you will learn how to use CasC to maintain a consistent and repeatable infrastructure configuration across different environments. This approach will help prevent drift in configuration, require approval before implementation, and ensure that both development and production deployments are well-maintained.
36+
37+
Automation controller before, a recomended place to start is this instruct lab, if you have not done so before:
1838
[Introduction to automation controller](https://developers.redhat.com/content-gateway/link/3884764)
1939

2040
# Agenda
@@ -24,16 +44,20 @@ Recommended agenda for when there is an instructor teaching.
2444
<table>
2545
<tbody>
2646
<tr>
27-
<td><b>Part 1</b>: Creating an Execution Environment</td>
28-
<td>⏱️ 45 minutes</td>
47+
<td><b>Part 1</b>: Creating the Basics for configuring the Automation Platform</td>
48+
<td>⏱️ 40 minutes</td>
49+
</tr>
50+
<tr>
51+
<td><b>Part 2</b>: Creating credentials, inventories, and job templates and everything that is needed to create them.</td>
52+
<td>⏱️ 40 minutes</td>
2953
</tr>
3054
<tr>
31-
<td><b>Part 2</b>: Configuring your Automation hub</td>
32-
<td>⏱️ 70 minutes</td>
55+
<td><b>Part 3</b>: Configuring the Automation hub to load more content</td>
56+
<td>⏱️ 30 minutes</td>
3357
</tr>
3458
<tr>
35-
<td><b>Part 3</b>: Configuring your Automation controller</td>
36-
<td>⏱️ 120 minutes</td>
59+
<td><b>Part 4</b>: Build an execution environment to be used on the platform.</td>
60+
<td>⏱️ 40 minutes</td>
3761
</tr>
3862
<tr>
3963
<td><b>Part 4</b>: Creating an Automation controller Workflow in code</td>
@@ -42,7 +66,7 @@ Recommended agenda for when there is an instructor teaching.
4266
</tbody>
4367
</table>
4468

45-
**Total Time**: 5.5 hours (330 minutes)
69+
**Total Time**: 4 hours (249 minutes)
4670

4771
## Lab Index
4872

@@ -58,7 +82,8 @@ Recommended agenda for when there is an instructor teaching.
5882
<tr>
5983
<td>Config as code Introduction to AAP</td>
6084
<td>Learn about the fundamentals of using Configuration of Code to maintain the Ansible Automation Platform</td>
61-
<td><a target="_new" href="(TBD)">🚀 Launch Lab</a></td>
85+
<td>This is a Red Hat or Partner Only Lab, and requires access to demo.redhat.com, please reach out to your account representative to coordinate access to the Lab</td>
86+
<td><a target="_new" href="https://catalog.demo.redhat.com/catalog?item=babylon-catalog-prod/summit-2025.lb2193-config-as-code-aap.prod&utm_source=webapp&utm_medium=share-link">🚀 Launch Lab</a></td>
6287
</tr>
6388
</tbody>
6489
</table>

‎exercises/instruqt/aapcasc.md‎

Lines changed: 0 additions & 135 deletions
This file was deleted.

0 commit comments

Comments
 (0)