Use Azimuth UI schema for integer constraint

stackhpc · Jul 12, 2024 · c78922b · c78922b
1 parent 43848b0
commit c78922b
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/chart/azimuth-ui.schema.yaml b/chart/azimuth-ui.schema.yaml
@@ -10,6 +10,12 @@ controls:
     type: MirrorControl
     path: /huggingface/model
     visuallyHidden: true
+  # Azimuth UI doesn't handle json type ["integer","null"]
+  # properly so we allow type "string" in JSON schema then
+  # constrain to (optional) integer here.
+  /api/modelMaxContextLength:
+    type: IntegerControl
+    required: false
 
 sortOrder:
   - /huggingface/model

diff --git a/chart/values.schema.json b/chart/values.schema.json
@@ -97,7 +97,7 @@
             "type": "object",
             "properties": {
                 "modelMaxContextLength": {
-                    "type": ["integer", "null"],
+                    "type": "string",
                     "title": "Model Context Length",
                     "description": "An override for the maximum context length to use if the model's default is not suitable."
                 },
@@ -106,7 +106,7 @@
                     "properties": {
                         "version": {
                             "type": "string",
-                            "title": "vLLM version override",
+                            "title": "Backend vLLM version",
                             "description": "The vLLM version to use as a backend. Must be a version tag from [this list](https://github.com/vllm-project/vllm/tags)",
                             "default": "v0.4.3"
                         }