Posts

Meta - Arguments

FOR EACH  resource "aws_s3_bucket" "bucket" {   for_each = ["bucket1", "bucket2", "bucket3"]   bucket = each.value   acl    = "private" } DEPENDS ON resource "resource_type" "example" {   # Configuration for this resource   depends_on = [resource_type.other_resource] } COUNT  resource "resource_type" "example" {   # Configuration for this resource   depends_on = [resource_type.other_resource] } PROVIDER resource "resource_type" "example" {   # Configuration for this resource   depends_on = [resource_type.other_resource] }

Azure Pipeline for Java build - test and deploy to staging

 # Trigger the pipeline on changes to the main branch trigger:   branches:     include:       - main # Define the VM image to use for the pipeline pool:   vmImage: 'ubuntu-latest' # Pipeline steps stages:   - stage: Build     jobs:       - job: Build         steps:           # Checkout the code from the repository           - checkout: self           # Set up Maven           - task: UseMaven@1             inputs:               mavenVersionOption: 'Default'               mavenPomFile: 'pom.xml'               goals: 'clean compile'           # Run tests           - task: Maven@3             ...

Key Vault Permissions

 key vault To manage Azure resources using Terraform, you need to ensure that your service principal or managed identity has the appropriate permissions for each block. Here’s a breakdown of the necessary permissions grouped by resource group and other scopes: Primary Subscription (azurerm.primary)     Resource Group: rg-esp-qa         Permissions:             Microsoft.Resources/subscriptions/resourceGroups/read     Resource Group: NET-EUS2-QA-RG         Permissions:             Microsoft.Resources/subscriptions/resourceGroups/read             Microsoft.Network/virtualNetworks/read             Microsoft.Network/virtualNetworks/subnets/read     Resource...

Service Bus Permission

 SERVICE BUS Resource Group Level Permissions     Resource Group: rg-esp-qa         Role: Custom role combining Network Contributor, Service Bus Contributor         Permissions:             Microsoft.Resources/subscriptions/resourceGroups/read             Microsoft.Resources/subscriptions/resourceGroups/write             Microsoft.ServiceBus/namespaces/write             Microsoft.ServiceBus/namespaces/read             Microsoft.Network/privateEndpoints/write             Microsoft.Network/privateEndpoints/read     Resource Group: NET-EUS2-QA-RG   ...

APIM permission

 APIM Resource Group Level Permissions     Resource Group: rg-esp-qa         Role: Custom role combining API Management Service Contributor         Permissions:             Microsoft.Resources/subscriptions/resourceGroups/read             Microsoft.Resources/subscriptions/resourceGroups/write             Microsoft.ApiManagement/service/write             Microsoft.ApiManagement/service/read     Resource Group: NET-EUS2-QA-RG         Role: Custom role combining Network Contributor         Permissions:             Microsoft.Network/virtualNetworks/...

code-1

Startoff- Azure- Terraform- Connectivity

 Yes, you can add connectivity configurations, such as service principal authentication details, to your Terraform file structure. Here's how you can organize your Terraform configuration files to include connectivity settings:   terraform/ ├── modules/ │   └── resource_group/ │       ├── main.tf │       ├── variables.tf │       └── outputs.tf ├── connectivity/ │   └── azure/ │       ├── main.tf │       └── variables.tf ├── dev/ │   ├── main.tf │   ├── variables.tf │   ├── outputs.tf │   └── terraform.tfvars ├── qa/ │   ├── main.tf │   ├── variables.tf │   ├── outputs.tf │   └── terraform.tfvars ├── uat/ │   ├── main.tf │   ├── variables.tf │   ├── outputs.tf │   └── terraform.tfvars └── p...