Shrikant RajKumar Tiwari

Yeah. Uh, I'm Shrighan Tiwari, and, uh, I have total around 7 7 plus years of experience. And currently, I'm working in TCS as a cloud, uh, cloud support engineer that is cloud operations team, wherein I am working with, uh, various teams. And I'm basically working at infrastructure, uh, as a support engineering infrastructure team and wherein we deal with the resource creation, like EC 2 instances in AWS, DNS hosted zones, uh, DynamoDB table, and the various instances, and also VPC. And in, uh, same in Azure also, we we, like, we create upon receiving the request, like,

Yeah. In order to create a create a job in, uh, like, which should trigger a infrastructure from Jenkins, Uh, basically, we'll have to create a Terraform script, uh, and that should be, uh, like, that should be, uh, uploaded in our central repository from that is in, uh, Jenkins. And whenever we run a pipeline, uh, that will help to create a resource.

In order to manage a Terraform state, the best practice is to create to create a separate bucket so that we can, uh, whenever a source is created using that particular Terraform script, the state file can be remotely stored in a particular, uh, storage bucket or, like, uh, in the s 3 bucket in AWS or a storage bucket in Azure. So which which will help to maintain the state of that particular Terraform, uh, resource. And whenever we make any changes or any other user is making any changes, so it will, uh, help to store the remote changes, uh, like, in a remote remote, uh, storage account so that, uh, it will be clutter free, and it will have to make make maintaining the most optimal state. And, also, we can use a kind of a telephone lock, which will allow which will not allow multiple users to make, uh, a changes on that particular Terraform resource at the same time. So if any pipe suppose, uh, if any pipeline is running currently for that particular Terraform script, so it will, uh, maintain a particular kind of a log on that state file so that no other person from the team can make any changes on

Uh, not sure. I haven't worked with Jenkins much, so I'm not aware.

Uh, I don't see any error in this.

Like, I'm not, uh, much away from my side. But, uh, in a normal scripting using any virtual any, like, a a code repository in the central repository, we can create a script and we can use to, uh, automate the deployment of the