From c0870e0156c483b0dc9fa05e3bb71067c9fc4010 Mon Sep 17 00:00:00 2001 From: Richard Cox Date: Fri, 18 Dec 2020 12:17:21 +0000 Subject: [PATCH] Helm Chart: Ensure mariadb port value can be set (#4844) * Helm Chart: Ensure mariadb port value can be set - fixes #4843 * Allow for missing mariadb.port Without this we get the opposite error ``` Error: values don't meet the specifications of the schema(s) in the following chart(s): console: - mariadb.port: Invalid type. Expected: integer, given: null ``` have now tested with and without mariadb.port and now in both cases we get the expected `DB_PORT` value in the rendered template --- deploy/kubernetes/console/values.schema.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy/kubernetes/console/values.schema.json b/deploy/kubernetes/console/values.schema.json index 1e217f637a..17c7ddeb6d 100644 --- a/deploy/kubernetes/console/values.schema.json +++ b/deploy/kubernetes/console/values.schema.json @@ -300,7 +300,7 @@ } }, "port": { - "type": "null" + "type": ["integer", "null"] }, "resources": { "type": "object",