Merge pull request #18 from jordlay/jl/add-null-to-common-issues

added null in cgvs to common issues

Author: jordlay

articles/operator-service-manager/media/cgv_error.png

@@ -170,3 +170,25 @@ There are multiple solutions available.
 - Edit your helm chart, or pass in the image paths in values.yaml, and set the image paths to match the repository structure in your source registry.
 - Upload the images to your source registry such that the concatenation of "image_sources" in the `cnf-input.jsonc` file and the image path from the helm chart matches the uploaded location in the source registry.
 - The AOSM CLI stores metadata for the images it discovers in `cnf-cli-output/artifacts/artifacts.json`. The path the AOSM CLI searches in the source registry is `<registry_name>/<registry_namespace>/<artifact_name>/<artifact_version>`. You can manually edit this file so that the values match the image's location in your source ACR.
+
+### CGVs don't match CGS when parameter has null type
+
+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. 
+
+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.".
+
+![Screenshot of the portal where there is an error message because the CGVs do not match the CGS](media/cgv_error.png)
+
+To fix this error, change `"null"` to `null` in the CGVs. 
+
+For example, originally we have the value `"null"`:
+
+```json
+"serviceAccount_name": "null",
+```
+Which must be changed to the value `null`.
+
+```json
+"serviceAccount_name": null,
+
+