Skip to content

Connect CD3 Container to Azure Subscription

Connecting the CD3 container to an Azure Subscription authenticates the toolkit, allowing it to create, update, or export resources from the azure portal.


🛠️ Steps:

1 - Login (Exec) into the Container

  • Login to the previously launched container using either RM Stack or Manual Launch.

    sudo podman exec -it cd3_toolkit bash

    sudo docker exec -it cd3_toolkit bash

2 - Edit connectAzure.properties

  • Run 

    cd /cd3user/oci_tools/cd3_automation_toolkit/

  • Fill the input parameters in connectAzure.properties file. Expand below tables for parameter description and sample data. Description for each parameter is also provided within the file.

📋 connectAzure.properties

Parameter Description
Parameter Description Example Mandatory
Parameter?
prefix Friendly name for the Azure Subscription demo Yes
subscription_id azure subscription id 155d83b2-....-....-....-ff5455dc5bdc No
tenant_id azure subscription tenant id 89b6314d-....-....-....-0c37ec95f20e No
client_id service principal appid 6950d59b-....-....-....-0039be18d7df No
client_secret service principal password .1..8Q~Xtch...........L5LxiPWb2vd_oaOP No


Important Configuration Tips- Offline tfvars Generation

  • Auth Details Parameters are optional.
  • If left empty, the toolkit will not be able to run any APIs against the Azure subscription.
  • This will mean that -
    Toolkit will be able to generate just the terraform (tfvars files) without having the ability to apply it. Also export workflow will not be executed.

4 - Initialise the environment

  • Initialise your environment to use the Automation Toolkit with Azure Cloud. 

    python connectCloud.py azure connectAzure.properties

    Heads-Up!

    • When running the CD3 container on a Linux VM host (without using the Resource Manager stack option), refer to point no. 7 under FAQ to avoid any permission issues.

Output:

Output files
Files Generated At File Path Comment/Purpose
setUpAzure.properties /cd3user/azure/<prefix>/<prefix>_setUpAzure.properties Subscription Specific properties file
Terraform files directory /cd3user/azure/<prefix>/terraform_files outdir for the generation of terraform files.
Variables File,Provider File, Root and Sub terraform modules /cd3user/azure/<prefix>/terraform_files/ Required for terraform to work. Variables file and Provider file will contain authentication parameters if provided while running above script.
out file /cd3user/azure/<prefix>/connectAzure.out This file contains a copy of information displayed as the console output of the script
connectAzure.properties /cd3user/azure/<prefix>/.config_files/<prefix>_connectAzure.properties The input properties file used to execute the script is copied to prefix folder to retain for future reference. This can be used when the script needs to be re-run with same parameters at later stage.
Example execution of the script Screenshot 2024-01-10 at 5 54 02 PM


Managing Multiple Prefixes?

Need to manage multiple environments separately by using distinct prefixes, all within a single CD3 container?
Check this out: Multiple Prefixes

Proceed to the below instructions:

Set Up Azure using Automation Toolkit