You can track the progress in the Azure DevOps portal. Use MGMT-WEEU-DEP00-INFRASTRUCTURE as the deployer configuration name and MGMT-WEEU-SAP_LIBRARY as the SAP library configuration name. Enter the configuration names for the deployer and the SAP library. Run the pipeline by selecting the Deploy control plane pipeline from the Pipelines section. The deployment uses the configuration defined in the Terraform variable files located in the WORKSPACES/DEPLOYER/MGMT-WEEU-DEP00-INFRASTRUCTURE and WORKSPACES/LIBRARY/MGMT-WEEU-SAP_LIBRARY folders. For this example, you can use samples/WORKSPACES. Open Azure DevOps and go to your Azure DevOps project.Įnsure that the Deployment_Configuration_Path variable in the SDAF-General variable group is set to the folder that contains your configuration files. You can't perform a control plane deployment from Windows. Run the following command to deploy the control plane:Įxport DEPLOYMENT_REPO_PATH="$" \ Set the environment variables for the service principal: The command adds the service principal details to the deployment key vault. Run the following command to create the deployer and the SAP library. #Defines the DNS suffix for the resources Note the Terraform variable file locations for future edits during deployment.Ī minimal Terraform file for the LIBRARY might look like this example: # The environment value is a mandatory field, it is used for partitioning the environments, for example, PROD and NP. # public_network_access_enabled controls if storage account and key vaults have public network access enabled # enable_firewall_for_keyvaults_and_storage defines that the storage accounts and key vaults have firewall enabledĮnable_firewall_for_keyvaults_and_storage = false # use_private_endpoint defines that the storage accounts and key vaults have private endpoints enabled # use_service_endpoint defines that the management subnets have service endpoints enabled # deployer_count defines how many deployer VMs will be deployed ![]() # deployer_enable_public_ip controls if the deployer Virtual machines will have Public IPs # management_bastion_subnet_address_prefix is the address prefix for the bastion subnet # management_firewall_subnet_address_prefix is the address prefix for the firewall subnet # management_subnet_address_prefix is the address prefix for the management subnet ![]() # management_network_address_space is the address space for management virtual network # The location/region value is a mandatory field, it is used to control where the resources are deployed You can copy the sample configuration files to start testing the deployment automation framework.Ī minimal Terraform file for the DEPLOYER might look like this example: # The environment value is a mandatory field, it is used for partitioning the environments. ![]() The sample SAP library configuration file MGMT-WEEU-SAP_LIBRARY.tfvars is located in the ~/Azure_SAP_Automated_Deployment/samples/Terraform/WORKSPACES/LIBRARY/MGMT-WEEU-SAP_LIBRARY folder. The sample deployer configuration file MGMT-WEEU-DEP00-INFRASTRUCTURE.tfvars is located in the ~/Azure_SAP_Automated_Deployment/samples/Terraform/WORKSPACES/DEPLOYER/MGMT-WEEU-DEP00-INFRASTRUCTURE folder. Prepare for the control plane deployment by cloning the repositories using the following commands: mkdir -p ~/Azure_SAP_Automated_Deployment cd $_ Optionally, assign the following permissions to the service principal: az role assignment create -assignee -role "User Access Administrator" -scope /subscriptions//resourceGroups/Īll the artifacts that are required to deploy the control plane are located in GitHub repositories. Record the output values from the command: The name of the service principal must be unique.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |