Is there a way to deploy the Azure Digital twin models,relationships and twins using ARM template.
As mentioned, creating models, twins, and relationships is considered a 'data plane' operation and is not available via ARM. You need to use SDKs, AZ CLI, or REST.
However, you can do those things via a "post deployment script" from an ARM deployment. For an example of how do that, see this deployment which has an ARM template that deploys the ADT instance (among other things) and then pre-creates a twin graph via a bash post-deployment script (despite it ending in .ps1, which is an error).
https://github.com/Azure-Samples/digital-twins-samples/tree/master/HandsOnLab/deployment
No, ARM templates are used to deploy infrastructure.
Azure Digital Twin models are deployed through SDKs, az cli commands and REST API calls.
Related
How can I automate Azure Logic Apps deployment using Ansible? Is there an option other that ARM templates via ansible?
Looks like the Azure Collection for Ansible doesn't support Logic Apps, so the ARM Template via Ansible would be the one way for now.
Since its open source, you could always contribute the module if you end up writing your own.
I have an ARM template which I can run as a custom deployment in the Azure portal. How do I get this to run automatically on a schedule? I'm guessing I can do it with an automation account, but I did not find anything in there about deploying ARM templates.
You have two (2) options:
Logic App
Runbook Automation
There is a post that shows how to implement this using either solutions.
I have a Linux Container-Based function app that I am deploying from an ARM template, I have found that I can enable "Continuous Deployment" via the Portal (screenshot below), but can't automate it with an ARM Template.
It would be really nice if we could automatically enable Continuous Deployment via the ARM template (or perhaps even enable it by default). Is there any way to do this?
I think you're right. It's not a property for Azure Web App, it's a trigger for the action event of the image registry. From the creation steps, you can find the webhook is created in the ACR or Docker hub which the web image in. The continuous deployment just provides a URL for the webhook. So you cannot set the Continuous Deployment in the ARM template in Azure.
For provisioning AWS services(EC2/R53/VPC/S3/..), technology like Terraform have unreliable approach in terms of performing rollback, error handling etc.
AWS CloudFormation templates address these problems.
CloudFormation templates are used for both provisioning of aws services(like EC2/VPC/r53/S3/...) and configuration of every service.
Additionally this template approach should easily fit into scripted pipeline using Jenkins.
What is the approach for provisioning and configuration of services in Azure cloud?
Its called Azure Resource Manager (Peter gave a helpful link in the comments). You will interact with ARM through Azure powershell, Azure Cli, ARM Templates, different SDK's or just plain rest calls to create resources.
ARM Templates are the closest thing you can get to CloudFormation templates, but they dont really have all the features of CloudFormation templates.
For example, there is no preview of the changes that will happen before you run the template. some services can not be configured with ARM Templates (or some of the properties cannot be configured).
I have an APIM instance and API's working on it. I want to create ARM template for deployment but can't understand how to do it. I only have the Azure portal repository for it and don't want to create a VSO repository. I am new to ARM templates, so don't have much information.
You can put all your code like the arm templates or swagger files wherever you want, GitHub, Azure DevOps, locally only ... and then deploy your api using Api-M's REST interface (https://learn.microsoft.com/en-us/rest/api/apimanagement/api/createorupdate), the PowerShell AzureRm or Az module https://learn.microsoft.com/en-us/powershell/module/azurerm.apimanagement/import-azurermapimanagementapi?view=azurermps-6.13.0 or by deploying an arm template.
When it comes to creating arm templates you may take a look here:
https://github.com/Azure/azure-quickstart-templates/blob/master/101-azure-api-management-create/azuredeploy.json
Anyway, we first started with arm templates as well and found later out that it's easier to use the REST interface or the PowerShell module by deploying a swagger file and the policies.