You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.yaml
-47Lines changed: 0 additions & 47 deletions
Original file line number
Diff line number
Diff line change
@@ -17,18 +17,6 @@ body:
17
17
Describe the issue you are experiencing here to communicate to the
18
18
maintainers. Tell us what you were trying to do and what happened.
19
19
Provide a clear and concise description of what the problem is. Please paste subset of playbook output (The failing task) so we can priotize and try to start troubleshooting.
20
-
- type: dropdown
21
-
validations:
22
-
required: true
23
-
attributes:
24
-
label: Issue Type
25
-
description: >
26
-
What kind of issue do you want to open?
27
-
options:
28
-
- Bug
29
-
- Documentation
30
-
- Feature Request
31
-
- Security Issue
32
20
- type: textarea
33
21
validations:
34
22
required: true
@@ -43,38 +31,3 @@ body:
43
31
label: Ansible Playbook Output
44
32
description: >-
45
33
Paste Ansible Playbook output
46
-
- type: markdown
47
-
attributes:
48
-
value: |
49
-
## Ansible Environment
50
-
- type: textarea
51
-
validations:
52
-
required: true
53
-
attributes:
54
-
label: Ansible Version
55
-
description: >-
56
-
Paste verbatim output from "ansible --version"
57
-
- type: textarea
58
-
validations:
59
-
required: true
60
-
attributes:
61
-
label: Ansible Configuration
62
-
description: >-
63
-
Paste verbatim output from "ansible-config dump --only-changed"
64
-
- type: dropdown
65
-
validations:
66
-
required: true
67
-
attributes:
68
-
label: Ansible Execution Node
69
-
description: >
70
-
Where is execution happening?
71
-
options:
72
-
- CLI Ansible (Ansible Core)
73
-
- Ansible Controller (previously known as Ansible Tower)
74
-
- type: textarea
75
-
validations:
76
-
required: true
77
-
attributes:
78
-
label: Operating System
79
-
description: >-
80
-
Are you running from RHEL, Ubuntu, MacOS? Provide details here.
Copy file name to clipboardExpand all lines: exercises/instruqt/aapcasc-4.md
+40-16Lines changed: 40 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,40 @@
1
1
# Configuration as Code for Ansible Automation Platform 2 Technical Workshop
2
2
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.
6
6
>
7
7
8
8
9
9
Welcome to our interactive lab on using Configuration as code to configure the Ansible Automation Platrom.
10
10
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.
12
26
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.
14
28
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.
16
30
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:
18
38
[Introduction to automation controller](https://developers.redhat.com/content-gateway/link/3884764)
19
39
20
40
# Agenda
@@ -24,16 +44,20 @@ Recommended agenda for when there is an instructor teaching.
24
44
<table>
25
45
<tbody>
26
46
<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>
29
53
</tr>
30
54
<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>
33
57
</tr>
34
58
<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>
37
61
</tr>
38
62
<tr>
39
63
<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.
42
66
</tbody>
43
67
</table>
44
68
45
-
**Total Time**: 5.5 hours (330 minutes)
69
+
**Total Time**: 4 hours (249 minutes)
46
70
47
71
## Lab Index
48
72
@@ -57,8 +81,8 @@ Recommended agenda for when there is an instructor teaching.
57
81
<tbody>
58
82
<tr>
59
83
<td>Config as code Introduction to AAP</td>
60
-
<td>Learn about the fundamentals of using Configuration of Code to maintain the Ansible Automation Platform</td>
<td>Learn about the fundamentals of using Configuration of Code to maintain the Ansible Automation Platform. 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>
0 commit comments