Specifying Azure Resource Manager parameters on the command line instead of in JSON files

Most of the Azure Resource Management template examples demonstrate using two JSON files. One file is the template definition that accepts a set of named parameters. The other file contains the parameter values.  The two files are accepted by the template engine and combined to create the actual definition.

The Azure CLI supports providing parameters in JSON files or as name/value pairs on the command line.  Parameters are always specified using --parameters. The command-line option supports two different syntaxes and can be invoked multiple times to provide property values from multiple JSON files and as command-line arguments.

The middle example represents invoking the CLI with the two filenames

The right-hand example represents involving the CLI with a template and a list of command-line parameter values. 

Refer to https://github.com/freemansoft/vnet-p2s-vpn-bastion-azure/blob/main/4-create-storage.sh

Pros and cons of JSON parameter files

Pros: 
  • You can check the parameter file into GitHub.  
  • You can create a parameter file for each different environment/tenant.
Cons:  
  • Each parameter file must provide exactly the parameters required by the template and no more. This means you can't create a common parameter file that is shared across templates. 
  • Scripts may have to construct parameter files if some of the parameter values can only be determined at invocation time.
  • Values are spread across multiple files.
  • No obvious way of inheriting parameter values from other parameter files.
Because of all this, I wanted to provide all of my parameter values as command-line arguments.

Azure CLI invoking ARM with command line parameters

This invocation submits a template by name along with 5 parameters.

az deployment group create --resource-group "$AZURE_RESOURCE_GROUP" \
     --template-file templates/template-log-analytics-workspace.json \
     --parameters \
     logAnalyticsWorkspaceName="$LOG_ANALYTICS_WORKSPACE_NAME" \
     lastPublishedAt="$NOW_PUBLISHED_AT"

Azure Resource Management Template - Parameter fragment

This template shows a parameter definition fragment from the template-storage.json file referenced in the section above.
{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",    "contentVersion": "1.0.0.0",
    "parameters": {
        "lastPublishedAt": {
            "type": "String",
            "metadata": {
                "description": "The last time the template was run"
            }
        },
        "logAnalyticsWorkspaceName": {
            "type": "String"
        },
        "location": {
            "type": "String",
            "defaultValue": "[resourceGroup().location]"
        }
    },
    "variables": {},
    "resources": [],
    "outputs": {}
} 

Video Explanation

Created 2021 /09

Comments

Post a Comment

Popular posts from this blog

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

DNS for Azure Point to Site (P2S) VPN - getting the internal IPs

Image
I wanted to access all my Azure resources without making any of them visible to the Internet.   The easiest give my local machine access to everything on my Azure Virtual Network (VNET) was to connect to it over VPN. It turns out creating Azure VPN gateways and connecting to Azure VPN endpoints is easy.  There are some subtleties in getting DNS name resolution to work that can confuse when first starting out. Setting the Stage There are a few ways to get to Azure endpoints and resources that are blocked from the internet.  We can  Create a Point-to-Site connection from our local machines to Azure Network Gateways Create a Site-to-Site network connection from our local networks to Azure Network Gateways. Use Bastion Hosts Use Cloud Shell Leave everything open to the internet. I chose a Point-to-Site (P2S) VPN connection that connects from my laptop to a VNet Gateway.  That joins my laptop
Read more