GitLab

Support issue_commission's `name' parameter for an optional description
of the commission. Include this field in the dict returned by
get_commission.

Change astakosclient accordingly.

Conflicts:
	astakosclient/astakosclient/__init__.py
	astakosclient/astakosclient/errors.py
	astakosclient/astakosclient/tests.py
	docs/index.rst

`snf-manage resource-import' does not provide a way to change the
default base quota any more. When importing a resource for the first
time, it sets the limit to zero.

Use `snf-manage resource-modify' to change limits. It supports both
interactive mode and reading limits from file, either for a specified
resource or for all resources.

Also remove unused `context' argument and replace empty list default
values with None.

in synnefo.settings.test

importing setting names explicitly makes it hard to write tests that
depend on specific setting values and polutes the module namespace.

In this commit only settings that are currently used in tests where
refactored.

- Avoid settings overrides from conf files inside SYNNEFO_SETTINGS_DIR
  Tests are expected to succeed with exact setting values defined either
  in tests modules/cases or in the default synnefo setting modules. To
  ensure this we temporarily set SYNNEFO_SETTINGS_DIR environmental variable
  to a non existing directory.
- Use DEBUG=False by default. We want our code to be tested in an
  settings environment as close to what we would set in a production
  deployment.
- Set initial astakos IM_MODULES setting to be able to test third party
  providers. This will be removed once we manage to dynamically run
  different tests with different IM_MODULES combinations

Everything should point to http://www.synnefo.org/*
This patch updates the URL everywhere in the repo.

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

All Exceptions that AstakosClient is raising should
be under AstakosClientException class

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.