Posts

Failover -- Azure Front Door

To set up failover in the scenario where you are using Azure Front Door or Azure Traffic Manager, you would typically follow these steps: Configure Health Probes : Set up health probes or monitoring endpoints for each of your backend services (e.g., web applications, APIs) in both the primary and secondary regions. These probes will regularly check the health and availability of your backend services. Define Failover Policies : Define failover policies based on the health status of your backend services. For example, if a backend service in the primary region becomes unhealthy or unavailable, you want traffic to automatically failover to the corresponding service in the secondary region. Configure Traffic Routing : In Azure Front Door or Azure Traffic Manager, configure traffic routing rules to direct incoming requests to the appropriate backend services based on your failover policies. For Azure Front Door, you can define routing rules using routing rules engine to specify conditions ...

Working on Azure -- Terraform - connectivity

If you're using a service principal account to authenticate with Azure, you'll still need to install the Azure CLI on your VDI, but you'll also need to configure the CLI to use the service principal for authentication. Here's how you can do it: Install Azure CLI : Download and install the Azure CLI on your VDI by following the installation instructions provided by Microsoft. You can find the installation instructions for various operating systems here . Authenticate with Service Principal : Once the Azure CLI is installed, you'll need to authenticate with Azure using the service principal credentials. Run the following command and provide the necessary details:  

Queries

Bugfix Branch : Bugfix branches are typically created to address non-critical issues or bugs identified during regular development cycles. These branches are often created off the main development branch (e.g., develop or dev ), allowing developers to isolate bug fixes from ongoing feature development. Bugfix branches follow the standard development process, including code review, testing, and merging changes back into the main branch through a pull request. Bugfix branches are part of the regular development workflow and are integrated into scheduled release cycles. Hotfix Branch : Hotfix branches are created to address critical issues that require immediate attention and deployment to production. These branches are typically created directly off the main branch (e.g., master or main ) or a release branch. Hotfix branches bypass the regular development process to expedite the resolution of critical issues. They may involve fewer code reviews or testing steps to minimize the time to ...

PR Approvals and deployment Approvals

  Hi Team, Just wanted to give you a heads up that I've sent over the CI/CD Terraform design and requirements document for your review. You should find it in your inbox now (or soon, depending on email delivery!). I'd appreciate it if you could take a look when you have a chance and let me know if you have any questions or feedback. I'm particularly interested in your thoughts on [mention a specific section or aspect of the document you'd like them to focus on]. No rush on this, but ideally it would be great to get your sign-off by [suggest a reasonable timeframe]. Thanks! Best, Terraform Workflow and Benefits for Azure Infrastructure Deployment Terraform is an open-source infrastructure as code (IaC) tool that allows you to define and manage infrastructure resources across multiple cloud platforms, including Azure. Here's a breakdown of the Terraform workflow and its advantages for deploying Azure infrastructure: Terraform Workflow: Configuration: Write configura...