In this blog, we will create an active-active infrastructure on Microsoft Azure using Terraform and Jenkins.
Prime Reasons to have an active-active set-up of your infrastructure
Disaster recovery (DR) is an organization’s method of regaining access and functionality to its IT infrastructure after events like a natural disaster, cyber attack, or even business disruptions just like during the COVID-19 pandemic.
Ensure business resilience No matter what happens, a good DR plan can ensure that the business can return to full operations rapidly, without losing data or transactions.
Maintain competitiveness Loyalty is rare and when a business goes offline, customers turn to competitors to get the goods or services they require. A DR plan prevents this.
Avoid data loss The longer a business’s systems are down, the greater the risk that data will be lost. A robust DR plan minimizes this risk.
Maintain reputation A business that has trouble resuming operations after an outage can suffer brand damage. For that reason, a solid DR plan is critical.
Browser: Chrome or Firefox or Brave? (Sorry Edge! :p )
Social Media: Facebook or Instagram?
In our daily lives, we always have choices, which one to use.
That was a brief intro about what we are going to read today. Yes, choices!
In Jenkins, while defining parameters, we can mention whether it needs to be a string parameter, a choice parameter, etc. These parameters will work on the input that you are mentioning in your job while running it. For example, if you are asking the user to choose between options A or B, the user chooses the parameter, and then Jenkins runs the script with that parameter.
This is a quick blog on how we can use the TruffleHog utility in our Jenkins pipeline to search for the secrets, passwords, sensitive keys which may have been accidentally committed in our repositories.
TruffleHog proves to be a great tool in helping us to fetch the sensitive data from our repositories which we do not want to expose at any cost.
Before moving further with this blog, I would like you all to take a look at the prerequisites that are mentioned below.
The world of DevOps is incomplete without ‘Continuous Integration’ and ‘Continuous Deployment’ after all these are among the building blocks of the methodology. When we talk about CI/CD the first name that comes to most peoples’ notice is Jenkins, one of the oldest and most flourished CI/CD tool in existence, however, there is one more name that’s picking up the pace as we talk, Azure DevOps, formerly known as Team Foundation Server. In this blog, we will see a detailed comparison of these two players and which one is your best fit.
Have you ever gone through the situation when your Jenkins goes down without any backup of your jobs and then you have to waste a lot of time and effort to re-create all your resources from scratch? We had also faced the same problem, but now We are free from it We have found a solution.
You might really want to know, how. What if, I say you can create a Jenkins server with the same configuration without any efforts and most importantly without wasting months, days, or even hours. Yes, you can set up your Jenkins in just 30 mins as we did.