Installing Programmatically

This is a Work-in-Progress

If you prefer not to deploy the service using ClickOps you may instead do a programmatic deploy.

Parameters are documented as follows:

location

Select and pass value of ‘location’ for the geography you want to deploy to from the table:

$ az account list-locations \
    --query '[?metadata.regionType == `Physical`].{location:name, name:displayName, status:metadata.regionCategory}' \
    --output table
customProviderLocation

One component of the deployed is limited in the geographies is is available in, so you should build a list of these regions using the following and pick the one closest to the geography you are deploying into.

No data is stored at this location and its only purpose is as an API endpoint 
$ az account list-locations \
  --query '[?metadata.regionType == `Physical`].{location:name, name:displayName}' \
  --output tsv \
  > locations.tsv
$ az rest \
  --uri /providers/Microsoft.CustomProviders \
  --uri-parameters api-version=2024-08-01 \
  --query "resourceTypes[?resourceType=='resourceProviders'].locations | [0]" \
  --output tsv \
  > crp-locations.tsv
$ grep -F -f crp-locations.tsv locations.tsv \
  | column -t -s "$(printf '\t')" -N Location,Name
vnet

FIXME

instances

Number of instances to use in provisioning the service, may be either one (1) or two (2) only.

vmDiskType

The disk type may be one of the following:

  • Standard_LRS: Standard HDD

  • StandardSSD_LRS: Standard SSD

  • Premium_LRS: Premium SSD

This is ignored if you choose an instance type that supports Ephemeral OS disks which are effective local SSDs and recommended where possible.