In Suse SLE 15.6, ansible can be installed either from the OpenSuse
repo of from PackageHub.

The version installed from OpenSuse requires Python >= 3.10.
Thus, it depends on the modern Python (version 3.11) provided by the
Python 3 module, instead of on the Python provided by the base system
module (version 3.6).
Packages installed for the modern Python, such as pip, will have
python311 as a prefix instead of just Python.

On the other hand, the ansible version in PackageHub is older and
can be used with the older Python version.

Thus, we check if either version of the package is installed, and if
not we install the more modern from those available.

See merge request nexedi/slapos.core!647.

also remove lab.node.vifib.com old URL. The URLs we support for gitlab
are:
 * lab.nexedi.com
 * lab.nxdcdn.com
 * lab.nexedi.cn

`SuSE-release` was deprecated and missing in new distributions in favor of `os-release`.

See merge request nexedi/slapos.core!628

Previous messages were all showing relative URL of the object on which the script was executed.
This was likely a typo in the script and made messages unreadable. This commit restores proper behaviour.

   Probably it comes from a bad copy and paste, since it contains mostly payzen references.

   Create the documents on the fly on the tests, otherwise it may cause problems on production.

  We don't want mistakes when configure it.

  No reason to pre-configure test like this

All outdated items should have a validation_state to validated

See merge request nexedi/slapos.core!642

This customization is no longer needed and the customized script is now
different in ERP5

  For now, we dont display Consumption details on invoice

   Use getMovementList to get Invoice Cell/Invoice Lines, it allows to get the
    aggregate properly.

   It makes list more consistent.

   Pay Now don't contain the link to pay anymore, so the user
   might use global action to make the payments anyway.

   Return translated 'state' directly and update tests

   Organisation is usually linked as Source Section or Destination
   Section.

   The user don't have access to the Organisations so use Shadow User
   (via script) to get the required information for the printout.

   Bare minimal update to display details, and extend to support Compute Node/Project/Instance Tree Subscriptions.
   Don't display details if the lines don't aggregate subscription requests

   Use directly the Destination Section and display more information if it was one Organisation

Do not try to show results with customer account for now.

Like a Subscription Request, a Subscription Change Request is used to create a new Open Sale Order,
but, it also archive a previous one at the same time.

The purpose is to change some parameters of an Open Sale Order,
and correctly created compensation movement, to ensure the resource
stock is correct.

Stop using discount resource, and reduce the quantity of the consumed software product / service

Only Sale people can create Subscription Change Request.

TODO: check how quantity precision can be defined

The only use case supported for now is changing an Instance Tree's user.

   for Sale Invoice Transaction

   Limit the access from any SHADOW user to specific SHADOW user linked into the context, same as Payment Transaction and Payzen events.

   Roles (Assignee and Auditor) don't change, just become more restrictive to single shadow user.