The performance impact is way to important, as it requires to
fetch all schema files.
For history, one use case was: 10 seconds to validate, 50ms to request.

Software releases should instead use the slapconfiguration:jsonschema
recipe to reject wrong input.
The recipe must use the schema informations stored on the installation directory.
slapos!1638

Move automated schema validation to the cli/request.py client.
Inform when the client start the parameter validation, to spot slowness.

No need to call everytime slapos node instance runs (every minute)

   rely on portal_template API to compareVersions

   Create a ticket if the SlapOS version into the monitored compute node is lower them minimal supported version found for the current master.

  If you access the listbox before the subscription request is indexed the link is broken on the listbox.

  patch provided by: Romain Courteaud.

It prevents Unauthorized, as only owner can access the temp object

  The code was rework to be visible by anonymous

the vulnerability database content seems to have changed

Stop and delete b2b services

- Support Slave Instance allocated in the same tree
- allow creating allocation consistency ticket on Instance Node
- handle allocation consistency for Slave Instance without Instance Node

This is a fixup of d42de18b.

history and statistics files are sometimes corrupted because of invalid json

We do 2 things to improve this:
 1. we use json.load to read the previous file (this will detect if the file is corrupted)
 2. we use json.dump to write the entire file at once in a temporary file and then we move this file to be atomic.

Probably this will consume more resources.

See merge request !728

  This prevents installation update modification date due Web Page
  modification date is newer.

  This fixes the coding style tests broken by:

    slapos_web_deploy: Added missing standalone-test
    slapos_web_deploy: Add rplc_coupler deploy script

  It was create a while ago, but never pushed.

Do not acquire from Person to an Organisation, as most user do not have access to the organisation_module

- directly show the software_release and sofware_type informations
- instance title is meaningless on this view, as admin want to get an understanding of which kind of software are instanciated
- drop creation_date, image columns