This folder contains ARM linked templates that can be used to stand up a specific resource and can be used in the same way as nested templated. A master template should call each template as a separate resource passing in parameters as necessary.
Sample master template snippet
"variables": {
"deploymentUrlBase": "https://raw.githubusercontent.com/SkillsFundingAgency/dfc-devops/master/ArmTemplates/"
},
"resources": [
{
"apiVersion": "2017-05-10",
"name": "myresource",
"type": "Microsoft.Resources/deployments",
"properties": {
"mode": "Incremental",
"templateLink": {
"uri": "[concat(variables('deploymentUrlBase'),'template.json')]",
"contentVersion": "1.0.0.0"
},
"parameters": {
}
}
}
]
Templates for root resources (ie resources that appear at the root of the Microsoft ARM reference documentation) are stored in the root folder. Any templates for child resources are stored in subfolders named after the root resource.
The following templates are available
- APIM Service
- APIM API
- APIM Logger
- APIM Product
- App Gateway v2
- App Insights
- App Service
- App Service Environment
- App Service Plan
- Azure Maps
- Azure Search
- CDN Profile
- CDN Endpoint
- Certificate
- Cognitive Services
- Container Registry
- Cosmos DB
- DataFactory
- DataFactory Linked Service Azure SQL
- DataFactory Linked Service CosmosDb
- Keyvault
- Keyvault Access Policy
- Keyvault Certificates
- Keyvault Secrets
- Network
- Public IP Address
- Redis Cache
- Service Bus
- Service Bus Firewall vNet Rule
- Service Bus Queue Auth Rule
- Service Bus Topic
- Service Bus Topic Subscription
- Service Bus Topic Auth Rule
- SQL Server Managed Instance
- SQL Server
- SQL Database
- Storage Account
- Storage Account Container
- Action Groups
- Failure Anomaly alerting rules
- Metric Alerts
- Slack Alert logic App