Skip to content

Commit 1dd0c02

Browse files
committed
Linting tidy ups
1 parent c83dcbb commit 1dd0c02

File tree

2 files changed

+6
-7
lines changed

2 files changed

+6
-7
lines changed

articles/operator-service-manager/quickstart-containerized-network-function-operator.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -202,7 +202,7 @@ In prior steps, you created a Managed Identity labeled identity-for-nginx-sns in
202202

203203
1. Under the **Privileged administrator roles**, category pick _Contributor_ then proceed with **Next**.
204204

205-
:::image type="content" source="media/privileged-admin-roles-contributor-resource-group.png" alt-text="Screenshot showing the privileged administrator role with contributor selected."::: lightbox="media/privileged-admin-roles-contributor-resource-group.png"
205+
:::image type="content" source="media/privileged-admin-roles-contributor-resource-group.png" alt-text="Screenshot showing the privileged administrator role with contributor selected." lightbox="media/privileged-admin-roles-contributor-resource-group.png":::
206206

207207
1. Select **Managed identity**.
208208

articles/operator-service-manager/troubleshoot-cli-common-issues.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -173,22 +173,21 @@ There are multiple solutions available.
173173

174174
### CGVs don't match CGS when parameter has null type
175175

176-
Currently, AOSM doesn't support `null` as a default value in deployParameters schema, which means that the default value `null` isn't allowed in Configuration Group Schemas either. To work around this issue, the AOSM CLI sets the default value for parameters of type null to be the string `"null"`, which allows an nfdv to publish successfully.
176+
Currently, AOSM doesn't support `null` as a default value in deployParameters schema, which means that the default value `null` isn't allowed in Configuration Group Schemas either. To work around this issue, the AOSM CLI sets the default value for parameters of type null to be the string `"null"`, which allows an nfdv to publish successfully.
177177

178-
When using the portal to create CGVs, your parameter autofills to have `"null"` as its value. If you don't change this value, the Portal shows an error message, saying: "New Configuration Group Value doesn't match the schema - please edit the values.".
178+
When using the portal to create CGVs, your parameter autofills to have `"null"` as its value. If you don't change this value, the Portal shows an error message, saying: "New Configuration Group Value doesn't match the schema - please edit the values."
179179

180-
![Screenshot of the portal where there is an error message because the CGVs do not match the CGS](media/cgv_error.png)
180+
:::image type="content" source="media/cgv_error.png" alt-text="Screenshot of the portal where there's an error message because the configuration group values don't match the configuration group schema." lightbox="media/cgv_error.png":::
181181

182-
To fix this error, change `"null"` to `null` in the CGVs.
182+
To fix this error, change `"null"` to `null` in the CGVs.
183183

184184
For example, originally we have the value `"null"`:
185185

186186
```json
187187
"serviceAccount_name": "null",
188188
```
189+
189190
Which must be changed to the value `null`.
190191

191192
```json
192193
"serviceAccount_name": null,
193-
194-

0 commit comments

Comments
 (0)