caf-terraform-landingzones/caf_solution/add-ons/azure_devops
Arnaud Lheureux 06f56f0d1c Update instructions path 2021-12-21 11:22:28 +00:00
..
documentation/images Add to root folder 2021-03-27 06:56:00 +00:00
scenario/200-contoso_demo Add to root folder 2021-03-27 06:56:00 +00:00
azdo.tf Add to root folder 2021-03-27 06:56:00 +00:00
azdo_agent_pools.tf Add to root folder 2021-03-27 06:56:00 +00:00
azdo_pipelines.tf Add to root folder 2021-03-27 06:56:00 +00:00
azdo_service_endpoint.tf Add to root folder 2021-03-27 06:56:00 +00:00
azdo_variable_groups.tf Add to root folder 2021-03-27 06:56:00 +00:00
backend.azurerm Add to root folder 2021-03-27 06:56:00 +00:00
locals.remote_tfstates.tf FMT 2021-08-16 08:00:34 +00:00
main.tf remove azurerm provider requirements 2021-12-07 10:17:57 +01:00
output.tf refactor aad_pod_identity and kustomization for aks add-ons 2021-07-23 10:30:45 +00:00
readme.md Update instructions path 2021-12-21 11:22:28 +00:00
solution.tf Update azure_devops 2021-04-13 11:29:10 +00:00
variables.tf Add to root folder 2021-03-27 06:56:00 +00:00

readme.md

Cloud Adoption Framework for Azure - Landing zones on Terraform - Azure Devops add-on

⚠️ This add-on is here for backward compatibility and will no longer be maintained. For new deployments, we recommend that you leverage the latest version available azure_devops_v1

The Azure Devops add-ons allow you to setup you Azure Devops environment as a platform to automate all your subsequent landing zone deployment from level 0 until level 4 through Azure pipelines with self hosted agents.

  • Azure Devops:

    • Agent Pools (Organization and Project Level)
    • Service Endpoint
    • Variables and Variable Groups
    • Pipelines
  • Azure (Connection with Azure Devops):

    • Azure AD Application
    • Custom Role
    • Keyvault and access policies for Azure AD App

Azure Devops add-on landing zone operates at level 0

For a review of the hierarchy approach of Cloud Adoption Framework for Azure landing zones on Terraform, you can refer to the following documentation.

Dependencies

Landing zone:

  • CAF Launchpad (Scenario 200 or above)

Azure Devops (example):

Azure:

  • PAT Token : PAT Token should be updated in keyvault secret that deployed by launchpad LZ as below

Deployment

rover -lz /tf/caf/caf_launchpad/add-ons/azure_devops \
  -tfstate azure_devops-contoso_demo.tfstate \
  -var-folder /tf/caf/caf_launchpad/add-ons/azure_devops/scenario/200-contoso_demo \
  -parallelism 30 \
  -level level0 \
  -env sandpit \
  -a apply


# If the tfstates are stored in a different subscription you need to execute the following command
rover -lz /tf/caf/caf_launchpad/add-ons/azure_devops \
  -tfstate_subscription_id <ID of the subscription> \
  -tfstate azure_devops-contoso_demo.tfstate \
  -var-folder /tf/caf/caf_launchpad/add-ons/azure_devops/scenario/200-contoso_demo \
  -parallelism 30 \
  -level level0 \
  -env sandpit \
  -a apply

We are planning to release more examples on how to deploy the Azure Devops Agents.