See merge request nexedi/slapos.core!396

See merge request nexedi/slapos.core!395

   Also add test for verify if user can close ticket by himself

   Change to use the proper API from ticket_slap_interface_workflow.

   Since the ticket could be seen by multiple users, don't force sender be the Ticket owner.

  Now the activities takes longer to run and configure the site

    It makes no sense now evaluate this using Grade System, but provide reports with helpful information  rather them evaluation.

See merge request nexedi/slapos.core!388

  Re-serialise the object from the dict after hit cache is slow enough
to cause problems ounder high load.

  This change preserve the previous behaviour reaching the final XML
from cache keeping performace on SlapTool and allowing new
implementation benefit from cache at same time.

  Fixup test to match xml with xml.

    This API extends catalog tool to search node and partitions using unrestricted search and accertACI.

    The mains goal here are:
       - raise Unauthorized (instead NotFound) when the object exists but you cannot have access
       - Globaly cache when you find a computer since this is quite intense operation
       - Be able to search regardless security (which is required for some usecases).

   The internal API only store dict, rather them store xml.

   slapos.slap.slap is only used on SlapTool context, releasing the
internal API on having it.

   The approach is deprecate the usage of it as soon clients relies on
  a different API.

$ slapos --version
slapos 1.7.7 (Python 3.9.2)

See merge request !389

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

See merge request !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 !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.