See merge request !389

  Those files tend to be modified quite often, including on the sub projects.

See merge request nexedi/slapos.core!387

 The site and translation data is updated after the installation,
 causing the delta. For now we ignore it and we update translation
 later.

   The purpose of the restricted parameters were to keep hidden values which weren't part of the schema on the parameter form, for a simplified version of the form.

   Since the user can always edit the raw values (over XML) this feature is undesirable, since if produce inconsistent outcome.

   It is the duty of software release to produce a simplified version, with a restricted list of acceptable parameters.

  Drop non required new line (it will be added anyway).

See merge request nexedi/slapos.core!385

  The "bad" sample are examples that are miss used, but it should still works (as expected by the format).

  The first example are from the implementation of boolean using enum + strings.

   Boolean should be handled as boolean not as strings.
   Selection should include default value even if they are outside the enum list.

   Keep the xml_output as it is even if the form is Invalid, this allow the user force post (since it is the user decision).

   If the textarea is blank/empty, add the default xml (empty values) in place, otherwise the user cannot re-render the parameter form back.

See nexedi/slapos.libnetworkcache@0fe8148a

slapos.libnetworkcache now needs the signature key to have a
corresponding certificate in signature-certificate-list so we need to
give signature_certificate_list to NetworkCacheClient constructor.

  Include more sample data.

   This makes eventual reuses for testing and demostration easy.

See merge request nexedi/slapos.core!384

   The kvm json schema is wrong, and it was fixed on a certain context, so I'm just dropping the assertion here until the software instance is refactored to use JSON in XML by default.

   This form allows you test any software release on the parameter form.

   This fixes up the support for the json schema definition for {"type": "number",  "enum": [ 1.0,  2.0] }

   It relies on data-format to overcome the limitation of select fields that only output strings on input.value.

   If the field is number the field is handled as float, and not as integer anymore.

See merge request nexedi/slapos.core!366

See merge request nexedi/slapos.core!382

See merge request nexedi/slapos.core!383

   We should use schema_url rather them json_url on validationJSON, since the json_url is the software.cfg.json while schema_url is the actual url for the schema.

  Like in WebSite_login, came_from is an URI Template so we must expand the URI to handle the {&n.me}
  that can be present on the URL.