pg 23 - github

Signed-off-by: Amndeep Singh Mann <[email protected]>

src/courses/profile-dev-test/21.md

@@ -1,6 +1,6 @@
 ---
-order: 22
-next: 23.md
+order: 21
+next: 22.md
 title: Test Kitchen - `kitchen.ec2.yml` File
 author: Aaron Lippold
 ---

src/courses/profile-dev-test/24.md → src/courses/profile-dev-test/23.md

@@ -1,19 +1,19 @@
 ---
-order: 24
-next: 25.md
-title: GitHub Actions
+order: 23
+next: 24.md
+title: 23. GitHub Actions
 author: Aaron Lippold
 ---
 
 ## GitHub Actions
 
 Our profile utilizes GitHub Actions as its primary CI/CD process. The Actions are separated by general business or process functions, allowing for a clear distinction between the workflow stages that we are testing.
 
-### [`lint-profile.yml`](.github/workflows/lint-profile.yml)
+### [`lint-profile.yml`](https://github.com/mitre/redhat-enterprise-linux-9-stig-baseline/blob/main/.github/workflows/lint-profile.yml)
 
 This action checks out the repository, installs Ruby and InSpec, then runs `bundle exec inspec check .` to validate the structure and syntax of the InSpec profile and its Ruby code.
 
-### [`verify-ec2.yml`](.github/workflows/verify-ec2.yml)
+### [`verify-ec2.yml`](https://github.com/mitre/redhat-enterprise-linux-9-stig-baseline/blob/main/.github/workflows/verify-ec2.yml)
 
 This action performs the following steps:
 
@@ -27,12 +27,6 @@ This action performs the following steps:
 8. Uploads the results to our Heimdall Demo server.
 9. Determines the success or failure of the test run based on the validation of the test suite results against the `threshold.yml` files for each test suite (`hardened` and `vanilla`).
 
-### [`verify-container.yml`](.github/workflows/verify-container.yml)
+### [`verify-container.yml`](https://github.com/mitre/redhat-enterprise-linux-9-stig-baseline/blob/main/.github/workflows/verify-container.yml)
 
-This action performs similar steps to `verify-ec2.yml`, with some differences:
-
-1. Configures access to the required container registries - Platform One and Red Hat.
-
-### [`verify-vagrant.yml.example`](.github/workflows/verify-vagrant.yml.example)
-
-This action is similar to the `verify-ec2` workflow, but instead of using a remote AWS EC2 instance in a VPC, it uses a local Vagrant virtual machine as the test target. The user can configure whether to upload the results to our Heimdall Demo server or not by modifying the GitHub Action.
+This action performs similar steps to `verify-ec2.yml`, with a key additional step of configuring access to the required container registries - Platform One and Red Hat.