Update howto-network-fabric-quality-of-service.md#4340
Conversation
Fixing errors in the QoS doc
|
@rkaraddi : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@rkaraddi : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 084e9fa: ✅ Validation status: passed
For more details, please refer to the build report. |
bartpinto
left a comment
bartpinto
left a comment
There was a problem hiding this comment.
A few recommendations below.
| - Fabric must be in a state that allows updates (not in an immutable provisioning phase). | ||
|
|
||
|
|
||
| ## Option 1—Azure CLI |
There was a problem hiding this comment.
It says "Option 1" but are there other options? I think it can be enabled at time of fabric create as well.
| @@ -33,16 +33,18 @@ | |||
|
|
|||
| ### Enable configuration lock: | |||
There was a problem hiding this comment.
This section should be before the update command is run.
| ## Prerequisites | ||
|
|
||
| - Use supported API and Fabric version. | ||
| - Fabric must be in a state that allows updates (not in an immutable provisioning phase). |
There was a problem hiding this comment.
Can we describe configuration locked as an example? Are there other states that allow update?
| --resource-group XXX_RESOURCE_GROUP \ | ||
| --resource-name XXX_FABRIC_NAME | ||
| ``` | ||
|
|
There was a problem hiding this comment.
Can we add a note that the commit will remove the configuration lock?
3 participants
Fixing errors in the QoS doc