Gitlab CI CD pipelines & Terraform - Part 3 (Basic Pipelines, Deploy terraform codes by CI/CD)

In this video utilizes GitLab CI/CD pipeline and terraform to deploy new project in Gitlab automatically and also the Terraform state will be stored in Gitlab as "http" backend. In Part 3, we learn to write a simple ci/cd pipeline for terraform codes step by steps.

The target of the video is:
- Understand the Jobs, Stages, Artifacts Concept
- Use CI/CD piplines to deploy terraform code

I started from scratch to install gitlab-runner and how to register it on local gitlab server and how to start to write basic CICD configuration file with learning how to use parameters like scripts, artifacts, variables, before_script ,"When" and image

Relate Video links:

[PortgueseProBF]

This is the best tutorials I have seen! Straight up to the point :) Thank you, so much!

[GopalKrishna-zeus]

Excellen Sir !! You explained very well ....excellent all three 3 video for gitlab is excellent and very learning. I appereciate your efforts to bring this video to the public.

[HoangLe-mansan]

your tutorials is the best ! come from zero to do the job !

[pallavkan]

excellent!! Best gitlab cicd tutorial with terraform

[munyororo]

Keep up the good work. I am now waiting to see more.

[chrisjchalifoux]

Love your video it is helping me out a lot

[George-mklp]

Just found this channel thanks for the great content

[leoestrada]

Very nice short videos, learning a lot! I am quite new to Terraform.
Question, I have multiple EC2 instances that are unrelated (kind of standalone from each other), most of them have diff specs.
I would like them to be managed via Terraform. Can you suggest an approach on how to manage them with Terraform and Gitlab CI pipelines?
The easiest I can think of is to create a project/repo for each EC2 instance and create each project/repo pipeline. However, that would be duplicating the Terraform EC2 codes. Is there a better way?

[neelojp]

Thanks a lot ;-) it’s possible to trigger this apply step at command line at min 11:52 ?

Can you maybe create part 4 .gitlab-ci.yml with advanced settings and only explain it please? That would be really helpful… thanks again خیلی ممنون آقای ماليك

[eashwerdev]

can you share the gitl code or the link to your repo please

[SanjeevKumar-hhg]

I have a job called plan-changes & I do NOT want this job to run when I do MR from branch to master.(when the master runs) ? The bellow snippet job
plan-changes: get executed for master branch which I do not want. The job plan-change runs on branch which is fine. How to avoid that the job does not run on Master ?.

.plan-changes:
# should be executed only on MergeRequest OR on a Branch & not on Master.
stage: plan
extends: [ .base, .not-master, .run-once-mr ]
before_script:
- *secrets
script:
# this is for checking the changes on a branch that is going to be merged. There should be not changes applied !
- terragrunt plan

.run-once-mr:
rules:
# always run MR pipeline
- if: $CI_PIPELINE_SOURCE == "merge_request_event"
# if it's a branch pipeline but there's an open MR on the source branch, don't run anything
- if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS
when: never
# if it's a branch pipeline and there's no open MR, run the branch pipeline
- if: $CI_COMMIT_BRANCH

.not-master:
rules:
- if: $CI_COMMIT_BRANCH != "master"