Skip to content

Commit d596bf4

Browse files
committed
fix suggestions
1 parent d0bf0a3 commit d596bf4

File tree

1 file changed

+13
-18
lines changed

1 file changed

+13
-18
lines changed

articles/operator-nexus/howto-cluster-manager.md

Lines changed: 13 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -27,17 +27,6 @@ This Azure region should be used in the `Location` field of the Cluster Manager
2727
## Limitations
2828
- **Naming** - Naming rules can be found [here](../azure-resource-manager/management/resource-name-rules.md#microsoftnetworkcloud).
2929

30-
## Global arguments
31-
32-
Some arguments that are available for every Azure CLI command
33-
34-
- **--debug** - prints even more information about CLI operations, used for debugging purposes. If you find a bug, provide output generated with the `--debug` flag on when submitting a bug report.
35-
- **--help -h** - prints CLI reference information about commands and their arguments and lists available subgroups and commands.
36-
- **--only-show-errors** - Only show errors, suppressing warnings.
37-
- **--output -o** - specifies the output format. The available output formats are Json, Jsonc (colorized JSON), tsv (Tab-Separated Values), table (human-readable ASCII tables), and yaml. By default the CLI outputs Json.
38-
- **--query** - uses the JMESPath query language to filter the output returned from Azure services.
39-
- **--verbose** - prints information about resources created in Azure during an operation, and other useful information
40-
4130
## Cluster Manager properties
4231

4332
| Property Name | Description |
@@ -46,18 +35,18 @@ Some arguments that are available for every Azure CLI command
4635
| managerExtendedLocation | The ExtendedLocation associated with the Cluster Manager |
4736
| managedResourceGroupConfiguration | Information about the Managed Resource Group |
4837
| fabricControllerId | The reference to the Network Fabric Controller that is 1:1 with this Cluster Manager |
49-
| analyticsWorkspaceId | The Log Analytics workspace where logs that are relevant to the customer will be relayed. |
50-
| clusterVersions[] | The list of Cluster versions that the Cluster Manager supports. It is used as an input in the cluster clusterVersion property. |
38+
| analyticsWorkspaceId | The Log Analytics workspace where logs that are relevant to the customer can be found. |
39+
| clusterVersions[] | The list of Cluster versions that the Cluster Manager supports. It's used as an input in the cluster clusterVersion property. |
5140
| provisioningState | The provisioning status of the latest operation on the Cluster Manager. One of: Succeeded, Failed, Canceled, Provisioning, Accepted, Updating |
5241
| detailedStatus | The detailed statuses that provide additional information about the status of the Cluster Manager. |
5342
| detailedStatusMessage | The descriptive message about the current detailed status. |
5443

5544
## Cluster Manager Identity
5645

57-
Starting with the 2024-07-01 API version, a customer can assign managed identity to a Cluster Manager. Both System-assigned and User-Assigned managed identities are supported.
46+
Starting with the `2024-07-01` API version, a customer can assign managed identity to a Cluster Manager. Both System-assigned and User-Assigned managed identities are supported.
5847

5948
If a Cluster Manager is created with the User-assigned managed identity, a customer is required to provision access to that identity for the Nexus platform.
60-
Specifically, `Microsoft.ManagedIdentity/userAssignedIdentities/assign/action` permission needs to be added to the User-assigned identity for `AFOI-NC-MGMT-PME-PROD` Microsoft Entra ID. It is a known limitation of the platform that will be addressed in the future.
49+
Specifically, `Microsoft.ManagedIdentity/userAssignedIdentities/assign/action` permission needs to be added to the User-assigned identity for `AFOI-NC-MGMT-PME-PROD` Microsoft Entra ID. It's a known limitation of the platform that will be addressed in the future.
6150

6251
The role assignment can be done via the Azure portal:
6352

@@ -106,6 +95,12 @@ Arguments:
10695
- **--mi-user-assigned** - Space-separated resource IDs of the User-assigned managed identities to be added.
10796
- **--if-match**/**if-none-match** - Specify the last-seen ETag value to prevent accidentally overwriting concurrent changes. The ETag is returned as the resource property once the resource is created and can be used on the update operations.
10897

98+
Common arguments that are available for every Azure CLI command:
99+
100+
- **--debug** - prints detailed information about CLI execution that is used for debugging purposes. If you find a bug, provide output generated with the `--debug` flag on when submitting a bug report.
101+
- **--output -o** - specifies the output format. The available output formats are Json, Jsonc (colorized JSON), tsv (Tab-Separated Values), table (human-readable ASCII tables), and yaml. By default the CLI outputs Json.
102+
- **--query** - uses the JMESPath query language to filter the output returned from Azure services.
103+
109104
### [Azure PowerShell](#tab/azure-powershell)
110105

111106
```azurepowershell-interactive
@@ -137,10 +132,10 @@ You can find examples of these two files here:
137132
- [clusterManager.parameters.jsonc](./clusterManager-parameters-jsonc-example.md)
138133

139134
>[!NOTE]
140-
>To get the correct formatting, copy the raw code file. The values within the clusterManager.parameters.jsonc file are customer specific and may not be a complete list. Please update the value fields for your specific environment.
135+
>To get the correct formatting, copy the raw code file. The values within the clusterManager.parameters.jsonc file are customer specific and may not be a complete list. Update the values for your specific environment.
141136
142-
1. In a web browser, go to the [Azure portal](https://portal.azure.com/) and sign in.
143-
1. From the Azure portal search bar, search for 'Deploy a custom template' and then select it from the available services.
137+
1. Open a web browser and go to the [Azure portal](https://portal.azure.com/) and sign in.
138+
1. Use the Azure portal search bar and type 'Deploy a custom template'. Select it from the available services.
144139
1. Click on Build your own template in the editor.
145140
1. Click on Load file. Locate your clusterManager.jsonc template file and upload it.
146141
1. Click Save.

0 commit comments

Comments
 (0)