s0sta
EN NL عربي
Filters
How to search
  • Plain words find names, texts and examples.
  • "two words" finds the exact phrase.
  • --name or -x finds an option.
  • #word looks only inside commands.
  • @grep finds lessons and labs that use grep.
  • Filters: cat:network · in:labs · in:notes · level:rhcsa · ch:8 · root:yes. Put ! before a word to leave it out. OR between words means one of them.
  • ↑ ↓ to move · Enter to open · Esc to close · / to search

Chapter 5Name in the course: Terraform, Git and CI/CD

Phase 3 (months 4–5): Terraform, Git and CI/CD

Phase 3 turns manual work into code and pipelines. Terraform builds the infrastructure, Git keeps every change, and GitHub Actions tests, scans and deploys on every push. The exam is Terraform Associate (004).

  • 4 Lessons
  • 0 Commands

$ run as a normal user# run as root (or with sudo)

Skills in this chapter

  • Terraform Associate (004) — months 4–5

5.1

Know the goal of phase 3

Any environment can be built, changed and destroyed from Git — with review, tests and security scans in the pipeline.

ItemValue
ExamHashiCorp Terraform Associate (004), tests Terraform 1.12 + HCP Terraform
FormatMultiple choice, 1 hour
Priceabout $70.50
Also learnGit, GitHub Actions, containers (Docker / Podman)

5.2

Study with these sources

The official HashiCorp study guide is free and complete. Git and Actions are learned by doing.

SourceUse it for
★ Terraform Associate (004) study guideFollow it in order
★ Terraform Get Started — AzureBuild real Azure resources with code
Terraform: Up & Running — Yevgeniy BrikmanThe best book on real Terraform work
★ Pro Git (free) + Learn Git BranchingGit from basics to rebase
★ GitHub Actions docs + GitHub SkillsThe CI/CD for the project
★ Docker — Get startedContainers before Kubernetes
My summariesTerraform, Git, GitHub Actions, Containers

5.3

Build the phase project

The staging environment of a real website (for example the company web shop) as code, with a full pipeline.

  1. Terraform for the Azure environment of phase 2: network, VMs or App Service, database, storage, monitoring.
  2. Remote state in an Azure storage account with locking; one workspace or folder per environment.
  3. A GitHub Actions pipeline: fmt, validate, a security scan of the Terraform code, plan on every pull request, apply after approval.
  4. Login to Azure with OIDC (no stored passwords), secrets only in GitHub environments.
  5. A container image of the app, built and scanned in the pipeline.
  6. Backups and monitoring included in the code.

Remember

The project matters more than the certificate: it shows a recruiter real, working automation.

5.4

Finish the phase

The phase is done when all of these are true.

  • [ ] Terraform Associate passed.
  • [ ] The staging environment can be built from zero with one pipeline run, and destroyed again.
  • [ ] Every change goes through a pull request with plan output and scan results.
  • [ ] The project README explains the design, the pipeline and the security choices.