GitLab

So that it follows the naming scheme of other astakosclient calls.

Assume a resource `astakos.pending_app' related to service `astakos'.
On submitting an application, issue a commission that will update the
related counter if possible, and accept the commission on success.
On approving/denying/cancelling an application, update the counter
likewise.

We always charge the application `owner'; however, if the `applicant'
is a project admin, we issue commission in force mode which succeeds
even if it exceeds the limit.

In order to pre-emptively check in the UI, follow the same process in
`dry run' mode, which issues a commission and rejects it on success.

Remove option of user-update to set its limit.

Refs #3349

It is the API code's task to transform the input dict to list.

Class structure is no more needed; there is no need for initialization,
since the code is used internally.

Also merge all migrations from 0026 to 0032.

All calls take a request_user (of type AstakosUser) argument.

Do not update holding limit if there exist user-specific base quota
for the particular resource.

Make sure that no Commission or Provision entry is created when
issue_commission fails, even if the transaction is committed.

The following indicators are returned for each holding:
"limit": the quota limit (as before)
"usage": the current usage (pessimistically, includes any pending
         allocations)
"pending": the difference of max and min allocation, indicates
           that there are pending commissions on this holding

Replace `available' by two fields: `limit' and `usage'.

also include services for which no existing presentation data exist.
Admin can use ASTAKOS_SERVICE_META setting to customize the service
presentation metadata.

Update view to use the introduced astakos quotas api.

Using this parameter, the service can query the quotas of a specific
user.

Rename it to fields.py and update all migrations that reference the field.

Remove quantity, import_limit, export_limit.
Update user-set-initial-quota management command.

Several fields of models Project and ProjectMembership were related
to the external syncing to quotaholder and have become obsolete since
the inclusion of quotaholder in astakos.

Returns quotas for all resources associated with the service that makes
the call.

- Remove presentation information from Service model (order, icon)
- To access the list of services filled with both presentation and api
  data use Service.catalog(). The method fills a dict with service
  identifiers and service metadata through the following steps
    - Initialize a service dict using
      astakos.im.presentation.service_defaults
    - Extend (merge and overwrite) it with the correspoding entry in
      astakos.im.presentation.SERVICES if exists.
    - Merge once again if user has set service metadata in
      ASTAKOS_SERVICE_META setting. This way user can change only the
      desired service parameters.

- An example of ASTAKOS_SERVICE_META containing keys which

    ASTAKOS_SERVICE_META = {
        'myservice': {
            'name': 'service_identifier',
            'url': 'https://service.url/service/ui/',
            'verbose_name': 'My service name',
            'order': 1,

            # cloudbar specific parameters
            'cloudbar': {
                'show': True,
                'title': 'My service name in cloudbar'
                # defaults to verbose_name
            },

            # dashboard specific parameters
            'dashboard': {
                'show': True,
                # we use different ordering in dashboard
                'order': 100,
                'description': 'My service description'
            }
        }
    }

- Updated dashboard to use Service.catalog() instead of hardcoded
  html.
- Updated service-* commands to keep up with model changes