kvm/theia: Dont use allOf on resilient to extend properties

  allOf implies that all (both) schemas should be valid, but
    additionalProperties false wont allow it, since it become multually
    invalid. (You can validate only one or None)

  Just use $ref to expand the list, it end up with the expected outcome
   reducing complexity.

  Note: kvm wasn't using additionalProperties false but it was changed
   because it makes it future proof, in case we set it (we should set).

software/kvm/instance-kvm-resilient-input-schema.json

 {
   "type": "object",
   "$schema": "http://json-schema.org/draft-06/schema",
-  "allOf": [
-    {
-      "$ref": "./instance-kvm-input-schema.json#"
-    },
-    {
+  "description": "Parameters to instantiate resilient KVM",
+  "additionalProperties": false,
   "properties": {
+    "$ref": "./instance-kvm-input-schema.json#/properties",
     "resilient-clone-number": {
       "title": "Amount of backup(s) to create",
       "description": "Amount of backup(s) to create. Each backup consists of a Pull Backup Server and a clone.",
@@ -58,6 +56,4 @@
       "optional": true
     }
   }
-    }
-  ]
 }

software/theia/instance-resilient-input-schema.json

@@ -2,11 +2,7 @@
   "$schema": "http://json-schema.org/draft-06/schema",
   "type": "object",
   "description": "Parameters to instantiate resilient Theia",
-  "allOf": [
-    {
-      "$ref": "./instance-input-schema.json#"
-    },
-    {
+  "additionalProperties": false,
   "properties": {
     "resilient-clone-number": {
       "title": "Amount of backup(s) to create",
@@ -59,8 +55,7 @@
       "type": "string",
       "default": "2W",
       "optional": true
+    },
+    "$ref": "./instance-input-schema.json#/properties"
   }
-      }
-    }
-  ]
 }

[Xavier Thompson]

I think this change is responsible for json-schemas now failing on master for theia and kvm.