| Status | |
|---|---|
| Build (Master) | |
| DTA | |
| Dev/Test | |
| PP | |
| PRD | |
| MO |
The templates hosted in this repository facilitate the deployment of the shared infrastructure for the Apprenticeships Service.
The deployment consists of two layers.
The subscription layer owns resources that are shared horizontally across a subscription and are used for management purposes. For example, Log Analytics, Azure Automation, KeyVault, Storage, Alerting, Dashboards etc.
Note: A subscription can contain one or more environments.
The environment layer owns resources that are shared vertically across an environment and are typically used to provide a platform for other independent applications. For example; App Service Plans, Virtual Networks, SQL Servers, ServiceBus etc.
There is a third layer that is not deployed by these templates. This is the application layer. Deployment templates for applications within this layer are typically stored with the application code as they will share the same lifecycle. These applications will often depend on infrastructure deployed by templates in this repository.
Both shared and application deployments consume templates from the platform building blocks repository.
The diagram below is a logical representation of the deployment template structure.
This is the primary method used to deploy the infrastructure. Configuration is stored securely either in the build definition or variable groups and versioned artifacts are used when deploying.
To deploy from your local machine, set each parameter as an environment variable then run the script below.
.\Initialize-SharedInfrastructureDeployment.ps1The expected environment variable names can be found in the metadata object for each parameter in subscription.template.json.
For example:
"resourceEnvironmentName": {
"type": "string",
"metadata": {
"description": "Base environment name. E.g. DEV. PP, PRD, MO. ",
"environmentVariable": "resourceEnvironmentName"
}
}Note: This deployment method should only be used for testing purposes.
Use the unit test runner to execute tests. The LocalDeployment switch will execute tests in a new process to avoid polluting the current runspace.
.\Start-UnitTest.ps1 -LocalDeploymentYou can specify specific tests by using the Path parameters.
.\Start-UnitTest.ps1 -Path .\Initialize-SharedInfrastructureDeployment.tests.ps1 -LocalDeploymentThe example above will execute the end to end mock deployment test.
New tests are automatically invoked at build time and the run will produce a test report which is published back to azure-pipelines in the context of the build.
The DTA stage deploys and tears down the infrastructure to provide a method for testing the deployment process without interferring with the availablity of the AT environment.