Merge pull request #1927 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 4/14

Author: ttorble

articles/postgresql/extensions/how-to-load-libraries.md

@@ -46,13 +46,19 @@ Using the [Azure portal](https://portal.azure.com):
 You can set `shared_preload_libraries` using the CLI [parameter set](/cli/azure/postgres/flexible-server/parameter#az-postgres-flexible-server-parameter-set) command.
 
 ```azurecli-interactive
-az postgres flexible-server parameter set --resource-group <resource_group> --server-name <server> --name shared_preload_libraries --value <extension_name>,<extension_name>
+az postgres flexible-server parameter set \
+  --resource-group <resource_group> \
+  --server-name <server> \
+  --name shared_preload_libraries \
+  --value <extension_name>,<extension_name>
 ```
 
 And can restart the server using the CLI [parameter set](/cli/azure/postgres/flexible-server#az-postgres-flexible-server-restart) command.
 
 ```azurecli-interactive
-az postgres flexible-server restart --resource-group <resource_group> --name <server>
+az postgres flexible-server restart \
+  --resource-group <resource_group> \
+  --name <server>
 ```
 
 ---

articles/postgresql/flexible-server/how-to-auto-grow-storage.md

@@ -55,7 +55,10 @@ Using the [Azure portal](https://portal.azure.com/):
 You can enable storage autogrow in an existing server via the [az postgres flexible-server update](/cli/azure/postgres/flexible-server#az-postgres-flexible-server-update) command.
 
 ```azurecli-interactive
-az postgres flexible-server update --resource-group <resource_group> --name <server> --storage-auto-grow enabled
+az postgres flexible-server update \
+  --resource-group <resource_group> \
+  --name <server> \
+  --storage-auto-grow enabled
 ```
 ---
 
@@ -88,7 +91,10 @@ Using the [Azure portal](https://portal.azure.com/):
 You can enable storage autogrow in an existing server via the [az postgres flexible-server update](/cli/azure/postgres/flexible-server#az-postgres-flexible-server-update) command. 
 
 ```azurecli-interactive
-az postgres flexible-server update --resource-group <resource_group> --name <server> --storage-auto-grow disabled
+az postgres flexible-server update \
+  --resource-group <resource_group> \
+  --name <server> \
+  --storage-auto-grow disabled
 ```
 
 ---
@@ -112,7 +118,10 @@ Using the [Azure portal](https://portal.azure.com/):
 You can enable storage autogrow while provisioning a new server via the [az postgres flexible-server create](/cli/azure/postgres/flexible-server#az-postgres-flexible-server-create) command.
 
 ```azurecli-interactive
-az postgres flexible-server create --resource-group <resource_group> --name <server> --storage-auto-grow disabled ...
+az postgres flexible-server create \
+  --resource-group <resource_group> \
+  --name <server> \
+  --storage-auto-grow disabled ...
 ```
 
 > [!NOTE]

articles/postgresql/flexible-server/how-to-configure-high-availability.md

@@ -81,19 +81,29 @@ You can enable high availability in an existing server via the [az postgres flex
 To enable high availability so that standby server is deployed in the same zone as the primary server, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server update --resource-group <resource_group> --name <server> --high-availability SameZone
+az postgres flexible-server update \
+  --resource-group <resource_group> \
+  --name <server> \
+  --high-availability SameZone
 ```
 
 To enable high availability with standby server deployed in a different zone than the primary server, and if you want the zone to be automatically selected, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server update --resource-group <resource_group> --name <server> --high-availability ZoneRedundant
+az postgres flexible-server update \
+  --resource-group <resource_group> \
+  --name <server> \
+  --high-availability ZoneRedundant
 ```
 
 Also, optionally, you can select the availability zone in which the standby server should be deployed. To do so, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server update --resource-group <resource_group> --name <server> --high-availability ZoneRedundant --standby-zone <standby_zone>
+az postgres flexible-server update \
+  --resource-group <resource_group> \
+  --name <server> \
+  --high-availability ZoneRedundant \
+  --standby-zone <standby_zone>
 ```
 
 If you're enabling high availability with zone redundancy, and the zone specified for standby matches the zone of the primary, you get this error:
@@ -171,7 +181,10 @@ You can disable high availability in an existing server via the [az postgres fle
 To disable high availability, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server update --resource-group <resource_group> --name <server> --high-availability Disabled
+az postgres flexible-server update \
+  --resource-group <resource_group> \
+  --name <server> \
+  --high-availability Disabled
 ```
 
 ---
@@ -211,13 +224,20 @@ You can enable high availability while provisioning a new server via the [az pos
 To deploy the primary server with a standby server in the same zone, and let the service choose for you the zone, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server create --resource-group <resource_group> --name <server> --high-availability SameZone ...
+az postgres flexible-server create \
+  --resource-group <resource_group> \
+  --name <server> \
+  --high-availability SameZone ...
 ```
 
 To deploy the primary server with a standby server in the same zone, and explicitly choose the zone, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server create --resource-group <resource_group> --name <server> --high-availability SameZone --zone <zone> ...
+az postgres flexible-server create \
+  --resource-group <resource_group> \
+  --name <server> \
+  --high-availability SameZone \
+  --zone <zone> ...
 ```
 
 If the availability zone specified isn't supported in the selected region, you get this error:
@@ -230,19 +250,31 @@ Message: Specified availability zone is not supported in this region. Please cho
 To deploy the primary server with a standby server in a different zone, and let the service choose for you both zones, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server create --resource-group <resource_group> --name <server> --high-availability ZoneRedundant ...
+az postgres flexible-server create \
+  --resource-group <resource_group> \
+  --name <server> \
+  --high-availability ZoneRedundant ...
 ```
 
 To deploy the primary server with a standby server in a different zone, explicitly specify the zone for the primary but let the service choose the zone for the standby, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server create --resource-group <resource_group> --name <server> --high-availability ZoneRedundant --zone <zone> ...
+az postgres flexible-server create \
+  --resource-group <resource_group> \
+  --name <server> \
+  --high-availability ZoneRedundant \
+  --zone <zone> ...
 ```
 
 To deploy the primary server with a standby server in a different zone, and explicitly specify the zone for the primary and the standby, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server create --resource-group <resource_group> --name <server> --high-availability ZoneRedundant --zone <zone> --standby-zone <standby_zone>...
+az postgres flexible-server create \
+  --resource-group <resource_group> \
+  --name <server> \
+  --high-availability ZoneRedundant \
+  --zone <zone> \
+  --standby-zone <standby_zone>...
 ```
 
 If you choose zone redundant high availability, and the same value is specified for the zones of the primary and standby servers, you get this error:
@@ -305,7 +337,10 @@ You can enable high availability while provisioning a new server via the [az pos
 To initiate a forced failover, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server restart --resource-group <resource_group> --name <server> --failover Forced
+az postgres flexible-server restart \
+  --resource-group <resource_group> \
+  --name <server> \
+  --failover Forced
 ```
 
 If you try to force a failover of an Azure Database for PostgreSQL flexible server that doesn't have high availability enabled, you get this error:
@@ -371,7 +406,10 @@ You can enable high availability while provisioning a new server via the [az pos
 To initiate a forced failover, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server restart --resource-group <resource_group> --name <server> --failover Planned
+az postgres flexible-server restart \
+  --resource-group <resource_group> \
+  --name <server> \
+  --failover Planned
 ```
 
 If you try to force a failover of an Azure Database for PostgreSQL flexible server that doesn't have high availability enabled, you get this error:

articles/postgresql/flexible-server/how-to-configure-index-tuning.md

@@ -55,7 +55,10 @@ You can enable index tuning in an existing server via the [az postgres flexible-
 To enable index tuning, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server index-tuning update --resource-group <resource_group> --server-name <server> --enabled true
+az postgres flexible-server index-tuning update \
+  --resource-group <resource_group> \
+  --server-name <server> \
+  --enabled true
 ```
 
 If the previous command executes successfully, you should see the following output:
@@ -99,7 +102,10 @@ You can disable index tuning in an existing server via the [az postgres flexible
 To disable index tuning, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server index-tuning update --resource-group <resource_group> --server-name <server> --enabled false
+az postgres flexible-server index-tuning update \
+  --resource-group <resource_group> \
+  --server-name <server> \
+  --enabled false
 ```
 
 If the previous command executes successfully, you should see the following output:
@@ -143,7 +149,9 @@ You can show the state of index tuning in an existing server via the [az postgre
 To disable index tuning, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server index-tuning show --resource-group <resource_group> --server-name <server>
+az postgres flexible-server index-tuning show \
+  --resource-group <resource_group> \
+  --server-name <server>
 ```
 
 If index tuning is enabled, you should see the following output:
@@ -183,7 +191,10 @@ You can show the value of a single index tuning setting in an existing server vi
 For example, to show the value of the index tuning setting called `analyze_interval`, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server index-tuning show-settings --resource-group <resource_group> --server-name <server> --name analyze_interval
+az postgres flexible-server index-tuning show-settings \
+  --resource-group <resource_group> \
+  --server-name <server> \
+  --name analyze_interval
 ```
 
 The command returns all information about the server parameter corresponding to that setting of index tuning, and the output is similar to the following:
@@ -214,7 +225,9 @@ Also, you can show the list of all index tuning settings in an existing server v
 To list all index tuning settings, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server index-tuning list-settings --resource-group <resource_group> --server-name <server>
+az postgres flexible-server index-tuning list-settings \
+  --resource-group <resource_group> \
+  --server-name <server>
 ```
 
 The command returns all server parameters that control the different settings of index tuning, and the output is similar to the following:
@@ -474,7 +487,11 @@ You can modify the value of a single index tuning setting in an existing server
 For example, to set the value of the index tuning setting called `analyze_interval` to `1440`, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server index-tuning set-settings --resource-group <resource_group> --server-name <server> --name analyze_interval --value 1440
+az postgres flexible-server index-tuning set-settings \
+  --resource-group <resource_group> \
+  --server-name <server> \
+  --name analyze_interval \
+  --value 1440
 ```
 
 The command returns all information about the server parameter corresponding to that setting of index tuning, and the output is similar to the following:

articles/postgresql/flexible-server/how-to-configure-managed-identities-system-assigned.md

@@ -143,7 +143,11 @@ Using the [Azure portal](https://portal.azure.com/):
 # Show the system assigned managed identity
 resourceGroup=<resource-group>
 server=<server>
-az postgres flexible-server identity list --resource-group $resourceGroup --server-name $server --query "{principalId:principalId, tenantId:tenantId}" --output table
+az postgres flexible-server identity list \
+  --resource-group $resourceGroup \
+  --server-name $server \
+  --query "{principalId:principalId, tenantId:tenantId}" \
+  --output table
 ```
 
 ---

articles/postgresql/flexible-server/how-to-configure-managed-identities-user-assigned.md

@@ -39,7 +39,10 @@ You can associate a user assigned identity to an Azure Database for PostgreSQL f
 resourceGroup=<resource-group>
 server=<server>
 identity=<identity>
-az postgres flexible-server identity assign --resource-group $resourceGroup --server-name $server --identity $identity
+az postgres flexible-server identity assign \
+  --resource-group $resourceGroup \
+  --server-name $server \
+  --identity $identity
 ```
 
 ---
@@ -64,7 +67,10 @@ You can dissociate a user assigned identity from an Azure Database for PostgreSQ
 resourceGroup=<resource-group>
 server=<server>
 identity=<identity>
-az postgres flexible-server identity remove --resource-group $resourceGroup --server-name $server --identity $identity
+az postgres flexible-server identity remove \
+  --resource-group $resourceGroup \
+  --server-name $server \
+  --identity $identity
 ```
 
 If you try to remove a user assigned managed identity which is used to access a data encryption key, you get the following error:
@@ -100,7 +106,10 @@ Using the [Azure portal](https://portal.azure.com/):
 # List all associated user assigned managed identities
 resourceGroup=<resource-group>
 server=<server>
-az postgres flexible-server identity list --resource-group $resourceGroup --server-name $server --query "userAssignedIdentities"
+az postgres flexible-server identity list \
+  --resource-group $resourceGroup \
+  --server-name $server \
+  --query "userAssignedIdentities"
 ```
 
 ---

articles/postgresql/flexible-server/how-to-configure-scheduled-maintenance.md

@@ -60,19 +60,28 @@ You can configure the maintenance schedule settings via the [az postgres flexibl
 To configure system managed schedule, use this command:
 
 ```azurecli-interactive
-az postgres flexible-server update --resource-group <resource_group> --name <server> --maintenance-window Disabled
+az postgres flexible-server update \
+  --resource-group <resource_group> \
+  --name <server> \
+  --maintenance-window Disabled
 ```
 
 To configure custom schedule, for a one hour window starting on Wednesdays at 2:29PM (UTC), use this command:
 
 ```azurecli-interactive
-az postgres flexible-server update --resource-group <resource_group> --name <server> --maintenance-window Wed:14:29
+az postgres flexible-server update \
+  --resource-group <resource_group> \
+  --name <server> \
+  --maintenance-window Wed:14:29
 ```
 
 To configure custom schedule, for a one hour window starting on Saturdays at midnight (UTC), use this command:
 
 ```azurecli-interactive
-az postgres flexible-server update --resource-group <resource_group> --name <server> --maintenance-window Wed
+az postgres flexible-server update \
+  --resource-group <resource_group> \
+  --name <server> \
+  --maintenance-window Wed
 ```
 
 ---