Mind-blowing & Hat's off to you to showcase this project step by step especially how Gitlab & Terraform hand to hand works in Production 😀❤. I have successfully created the same .
@@cloudchamp any problem that I run into regarding my projects and it's like you already know the problem and when I come to TH-cam for research the solution is there. I am starting to love DevOps because of you.
This tutorial offers an in-depth look at automating Terraform deployments using CI/CD pipelines. As a DevOps engineer, I appreciate the clear explanations and practical examples that make it easy to integrate Terraform with GitLab. The tutorial covers everything from initial setup to best practices for managing infrastructure as code, making it an invaluable resource for anyone looking to streamline their cloud deployments. Highly recommended for those aiming to enhance their DevOps workflows!"
Awesome 👌 content bhai and funny thing is when the destroy was running the bgm was perfect sync 😂 And yes today itself I'll do this project and definitely tag you nasi bhai ❤
Fantastic tutorial! Thank you! This really helped. Yours was the most comprehensive explanation I've seen so far and just you breaking down the code of the gitlab-ci file line by line in your review was incredibly helpful. So many tutorials I've watched skim over the important details and skip steps or just fail to elaborate on what their code is doing, which contributes to the confusion. My only confusion and question is about your destroy job. How did your destroy job run without a state declared? When I tried to run mine, it would "succeed" but only as a false positive. The destroy job wasn't finding the terraform state from the previous jobs and thinking there were 0 things to destroy. I had to troubleshoot and eventually added the state as an artifact in the apply job which resolved my issues. Liked, Subscribed and even bookmarked this particular tutorial!
@@karthickmuthiah7241 When you write your stages out you need to simply add an artifact path. Each stage of your CI/CD pipeline is going to stand up a new runner container so the runner in your apply stage and destroy stage won't have the terraform state file from the plan stage unless you declare it as an artifact to pass to the next stage. Like this: stages: - validate #simply validate that terraform is available - plan #create your plan file and state - apply #run your terraform apply - destroy #tear down your state build Example code: plan: stage: plan script: - terraform plan -state=$STATE -out="planfile" artifacts: paths: - planfile - state # This artifacts path variable will pass $STATE created in the script command to the next (apply) stage. Each stage will need to continue to pass the artifact. So, if you create a state in the plan stage you'll need to declare it as an artifact for apply to have access to it. If you have additional stages (such as destroy used here) then you would also have to declare it as an artifact in your apply stage to ensure that it continues to pass on into your destroy stage. Otherwise, your destroy won't be able to tear down the build from the apply stage as it no longer has that state file. Hope this helps.
on point as always, short and crisp and helpful, one question @cloudchamp, which CI/CD tool is mostly used in organization i have created similar projects using jenkins, github actions and gitlab, which CI/CD tool would you suggest to work on?
apply: stage: apply script: - terraform apply -input=false "planfile" dependencies: - plan the dependencies is not needed since apply and plan are in different stage so if plan stage failed the following stages will fail too if we put the plan and apply in the same stage then we need to add the dependecies line
I'm getting this error Missing newline after argument 3: resource = "AWS_instance" "server" { An argument definition must end with a newline Please help me with this
While creating the pipeline. 31.53 timestamps. how did you get the image name and the path? i tried looking that in your previous video but coudnt find it. i'd appreciate if you help me here.
Great Tutorial. I have created the terraform scripts, when I push the repo to gitLab I am getting ! [remote rejected] dev -> dev (pre-receive hook declined) error: failed to push some refs to 'gitlab remote repo path", please can you help me to resolve this issue
I did configured and showed you how to connect in this Gitlab Tutorial: Learn Complete GitLab CI/CD in 1 hour | GitLab CI CD Tutorial th-cam.com/video/JWXVijJfnHc/w-d-xo.html
Excellent video Nasi, it helped me a lot! I just have one question left, in your repository there's a variable TF_VAR_gitlab_token: ${GITLAB_ACCESS_TOKEN} which I was particularly interested in seeing its configuration, but you didn't mention it in the video. Is there another video about it or could you explain it to me here? Thank you very much!
Instead of calling the child module vpc (source=./vpc) inside web/mani.tf, why did you call source=./vpc inside main.tf (CICDTF/main.tf) Kindly explain me this brother..
I have just read the pre-requisites. My question is that I don't know about GitLab because I haven't used it. So can this project be done with Jenkins also or GitLab is mandatory?
Hi Nasi, i am almost there. But getting state lock error in the destroy stage. Not very sure how i can pass -lock=false for this stage manually. This work fine manually i can run this. Now im running the full pipeline and it started failing in the plan job itself saying state lock. Any leads please?
You can manually release the lock using terraform force-unlock command with the lock Id. -lock=false is not recommended in production environments where you have multiple people working together Let me know if still facing issue.
@@cloudchamp yes force-unlock is my first choice but silly thing is i am unable to find the lockid either in the error or state file. Below is the error i get if i run plan and cant see lock id. "Error: Error acquiring the state lock │ │ Error message: 2 errors occurred: │ * ResourceNotFoundException: Requested resource not found │ * ResourceNotFoundException: Requested resource not found │ │ │ │ Terraform acquires a state lock to protect the state from being written │ by multiple users at the same time. Please resolve the issue above and try │ again. For most commands, you can disable locking with the "-lock=false" │ flag, but this is not recommended."
Great tutorial! If I am using Windows where do I find where my binaries and dependencies are when defining them (entrypoint) in the gitlab.ci.yml file?
nice video man, i have a question, why didnt you define any triggers? or is the gitlab CI runs automatically when you push on the main branch by default?
It is a good project to automate the IAC though how can we configure the automation of the BE & FE codebase as well? So that whenever I commit any changes in my code base automation directly updates the code in EC2.
Good explanation....really concise and articulate....gets to the point and also explains prerequisite videos and concepts to understand... enjoyed it! Will watch all from the all others... just subscribed!
Crisp & Clear. Thanks mate. And please dont take me wrong your talking speed has really reduced to good level compared to initial videos and this helps learners like us to understand thoroughly. Being in the industry for 6+ years have hardly found good live projects. Please keep them coming! Thank you! All the best!
Mind-blowing & Hat's off to you to showcase this project step by step especially how Gitlab & Terraform hand to hand works in Production 😀❤. I have successfully created the same .
this guy deserves the highest award ever in the field of devops. simplifying such complicated concepts.
🤝🤝
@@cloudchamp any problem that I run into regarding my projects and it's like you already know the problem and when I come to TH-cam for research the solution is there. I am starting to love DevOps because of you.
@@ahmadqayyum7505 This comment is the reason i create content for!
@@cloudchamp thank you so much.
@@cloudchamp also can you make a playlist on Kubernetes for beginners, if you haven't made one already???
This tutorial offers an in-depth look at automating Terraform deployments using CI/CD pipelines. As a DevOps engineer, I appreciate the clear explanations and practical examples that make it easy to integrate Terraform with GitLab. The tutorial covers everything from initial setup to best practices for managing infrastructure as code, making it an invaluable resource for anyone looking to streamline their cloud deployments. Highly recommended for those aiming to enhance their DevOps workflows!"
🙏🙏
I love your tutorials. Simpe, clear and straight foward. One of the best tutorial for devops on the net. Please keep them coming
Thanks! Means a lot!!
Let's see who can complete this first..... 👀
Please Like & share :)
Crisp, Clear, Amazing, Mind-Blowing
What a tutorial, Loved It ❤
Glad you liked it
Make sure to share & subscribe 👍🏻
men.. i am so amazed at your skill set you need to do a bootcamp.. thank you so much for knowledge shared.
Thank you means a lot!
You explain it so perfectly bro 👍
Thank you 🙌
great tutorial. everything is explained in so detail. thank you so much
You're very welcome!
parce, como diriamos en Colombia, usted es una chimba! gracias por tus videos! 👍
Thanks brother 😎
Thanks for the wonderful session and project use case. I have implemented it in my home lab.
Wonderful!
This is very much needed project brother 👍
Definitely
very interesting video . Gives very good key concepts in a very clear way. I'll put these in practise pretty soon, Thanks!
Let me know how it goes 👍🏻
Thanks for this devops project 👍
My pleasure
Excellent project. Thank you, bro.
Glad you like it!
Amazing tutorial brother. Keep up the good work.
Appreciate it!
Awesome 👌 content bhai and funny thing is when the destroy was running the bgm was perfect sync 😂
And yes today itself I'll do this project and definitely tag you nasi bhai ❤
Thanks 😅
amazing work :)
Thanks
Great tutorial, thanks
You're welcome!
Fantastic tutorial! Thank you! This really helped. Yours was the most comprehensive explanation I've seen so far and just you breaking down the code of the gitlab-ci file line by line in your review was incredibly helpful. So many tutorials I've watched skim over the important details and skip steps or just fail to elaborate on what their code is doing, which contributes to the confusion. My only confusion and question is about your destroy job.
How did your destroy job run without a state declared? When I tried to run mine, it would "succeed" but only as a false positive. The destroy job wasn't finding the terraform state from the previous jobs and thinking there were 0 things to destroy. I had to troubleshoot and eventually added the state as an artifact in the apply job which resolved my issues.
Liked, Subscribed and even bookmarked this particular tutorial!
Hi, can you please share the steps of how you added the state as an artifact in yaml file
@@karthickmuthiah7241 When you write your stages out you need to simply add an artifact path. Each stage of your CI/CD pipeline is going to stand up a new runner container so the runner in your apply stage and destroy stage won't have the terraform state file from the plan stage unless you declare it as an artifact to pass to the next stage.
Like this:
stages:
- validate #simply validate that terraform is available
- plan #create your plan file and state
- apply #run your terraform apply
- destroy #tear down your state build
Example code:
plan:
stage: plan
script:
- terraform plan -state=$STATE -out="planfile"
artifacts:
paths:
- planfile
- state # This artifacts path variable will pass $STATE created in the script command to the next (apply) stage.
Each stage will need to continue to pass the artifact. So, if you create a state in the plan stage you'll need to declare it as an artifact for apply to have access to it. If you have additional stages (such as destroy used here) then you would also have to declare it as an artifact in your apply stage to ensure that it continues to pass on into your destroy stage. Otherwise, your destroy won't be able to tear down the build from the apply stage as it no longer has that state file. Hope this helps.
19:30 waiting for the second part to create keys as per the flow 😊
Great job bhai 🎉
Thanks
I will try this project today bro
👍🏻 yes!
Great one! Keep up the good work bro.
Thanks, will do!
only one Thala @ Abhishek Vermalla
Thanks brother
Welcome
Thank you for everything you do
You are so welcome
on point as always, short and crisp and helpful, one question @cloudchamp, which CI/CD tool is mostly used in organization i have created similar projects using jenkins, github actions and gitlab, which CI/CD tool would you suggest to work on?
Thank you very much brother.it really helps me to understand how terraform works...
You are most welcome
thank you!
You are welcome 🤗
Appreciate it, nice work.
Much appreciated!
Thanks❤❤❤❤❤
You are welcome 🤗
Lmk if you need help or you complete the project 👍🏻
apply:
stage: apply
script:
- terraform apply -input=false "planfile"
dependencies:
- plan
the dependencies is not needed since apply and plan are in different stage so if plan stage failed the following stages will fail too
if we put the plan and apply in the same stage then we need to add the dependecies line
Great explanation!
Thanks 😊
I'm getting this error
Missing newline after argument
3: resource = "AWS_instance" "server" {
An argument definition must end with a newline
Please help me with this
While creating the pipeline. 31.53 timestamps. how did you get the image name and the path? i tried looking that in your previous video but coudnt find it. i'd appreciate if you help me here.
Thank you 🙏
You’re welcome 😊
Great Tutorial. I have created the terraform scripts, when I push the repo to gitLab I am getting ! [remote rejected] dev -> dev (pre-receive hook declined)
error: failed to push some refs to 'gitlab remote repo path", please can you help me to resolve this issue
how can i reuse the same pipeline to deploy multiple environments with the same resources?
you didnot configure any runner on this pipeline, which runner is it using ? thanks
I did configured and showed you how to connect in this Gitlab Tutorial:
Learn Complete GitLab CI/CD in 1 hour | GitLab CI CD Tutorial
th-cam.com/video/JWXVijJfnHc/w-d-xo.html
Bro which tool you used for project documentation in ubuntu 22.04?.
Excellent video Nasi, it helped me a lot! I just have one question left, in your repository there's a variable TF_VAR_gitlab_token: ${GITLAB_ACCESS_TOKEN} which I was particularly interested in seeing its configuration, but you didn't mention it in the video. Is there another video about it or could you explain it to me here? Thank you very much!
Instead of calling the child module vpc (source=./vpc) inside web/mani.tf, why did you call source=./vpc inside main.tf (CICDTF/main.tf)
Kindly explain me this brother..
I have just read the pre-requisites. My question is that I don't know about GitLab because I haven't used it. So can this project be done with Jenkins also or GitLab is mandatory?
Gitlab is mandatory as it is in this video but you can do it on Jenkins too
Bro which tool used for documenting in ubuntu!!?.
Do u have any videos ro learn terraform please for a beginner ,appreciate it
Absolutely I do, check out the playlist or a 60 mins video
@cloudchamp Thank you very much ,i will start watching them videos , ,is it possible to learn that in one month for a beginner
Did you create s3 and dynamoDB manually or via terraform code?
Manually in this video but also have another terraform backend video where it’s done in terraform 👍🏻
15:09
Hi Nasi, i am almost there. But getting state lock error in the destroy stage. Not very sure how i can pass -lock=false for this stage manually. This work fine manually i can run this. Now im running the full pipeline and it started failing in the plan job itself saying state lock. Any leads please?
You can manually release the lock using terraform force-unlock command with the lock Id.
-lock=false is not recommended in production environments where you have multiple people working together
Let me know if still facing issue.
@@cloudchamp yes force-unlock is my first choice but silly thing is i am unable to find the lockid either in the error or state file. Below is the error i get if i run plan and cant see lock id. "Error: Error acquiring the state lock
│
│ Error message: 2 errors occurred:
│ * ResourceNotFoundException: Requested resource not found
│ * ResourceNotFoundException: Requested resource not found
│
│
│
│ Terraform acquires a state lock to protect the state from being written
│ by multiple users at the same time. Please resolve the issue above and try
│ again. For most commands, you can disable locking with the "-lock=false"
│ flag, but this is not recommended."
something silly im missing.
nasi can you share some resource to learn golang
Hey bro ur discord link expired can u update it
bro why dont u explain in super putty
It’s the same when you do it in Linux machine mine is Ubuntu 20
sometimes it give this error error configuring S3 Backend: no valid credential sources for S3 Backend found. how to solve this
Great tutorial! If I am using Windows where do I find where my binaries and dependencies are when defining them (entrypoint) in the gitlab.ci.yml file?
Sir give me fyp idea using devops and cloud
Eg . Cloud infrastructure
can you explain the 'entry point' value on the gitlab yml. I got a bit lost and wasn't sure how you got that value
Hey, Brother!
I am also DevOps engineer, Could you please tell me which terminal are you using, It's Looking Good Though!
I am using inbuilt terminal . I have Ubuntu 22 in my local
can you please do a similar one for github CICD. Thanks a ton
nice video man, i have a question, why didnt you define any triggers? or is the gitlab CI runs automatically when you push on the main branch by default?
yes it does once theres a code change to main
bruh were did you learn devops course
Just took my SAA-003 certification. Watching your videos to conquer my first IT job and portfolio
Best of luck to you brother
@@cloudchamp tks bro!
Clear cut explanation do more videos
Thank you, I will
It is a good project to automate the IAC though how can we configure the automation of the BE & FE codebase as well? So that whenever I commit any changes in my code base automation directly updates the code in EC2.
Can I do this project in windows 11
Yes
Good explanation....really concise and articulate....gets to the point and also explains prerequisite videos and concepts to understand... enjoyed it! Will watch all from the all others... just subscribed!
Thanks man!
Happy to help 😀
This is amazing and exactly what I needed except I'm trying to use gitlab it self as backend!
Glad it was helpful!
Crisp & Clear. Thanks mate.
And please dont take me wrong your talking speed has really reduced to good level compared to initial videos and this helps learners like us to understand thoroughly.
Being in the industry for 6+ years have hardly found good live projects. Please keep them coming!
Thank you! All the best!
Thanks for this helpful feedback 😀
You are too fast bro
Please adjust the playback speed on TH-cam setting
Ok bro.