GitLab

`snf_django.lib.api.urls.api_patterns` acts as django `patterns` method
used commonly in urls modules. Using api_patterns to register urls will
result all patterns to be exempted from csrf protection.

method does not seem to exist in debian packaged django release. Since
csrftoken is not used in 500 templates the removal won't cause any side
effects.

The service definitions of astakos are not actually within
the astakos package, but in astakosclient.
The reason for this is that every other component needs
some knowledge about astakos' services, and the only common
astakos-related package they depend is astakosclient.

automatically detect which cloudbar menu is active by matching the current
window location with the registered service url.

- Move 404, 500 templates from astakos to webproject
- Remove 404, 500 templates from pithos-app
- Webproject now includes static files to serve jquery as an asset in 404, 500
  pages.
- Custom 500 handler. Use RequestContext if possible.

redirect user to landing page by default

A data migration was mistakenly squashed in schema migration, causing
problems with newer south versions. This data migration is not needed
in a production system, because it affects only a table introduced in
the same Synnefo version as this migration (v0.13).

Adapt script snf-register-components to update/import services for
an already registered component.

optionally append a redirect view to the root url of the project. Redirect url
is configurable using WEBPROJECT_ROOT_REDIRECT setting.

extend_with_root_redirects can be used by components to easily extend the
registered urlpatterns with utility redirect views for the root urls.

in api access view

no longer needed

- Direct access to user uuid is no longer useful to the users.
- `auth token`, `auth token expires` and `renew token action` are now accessed
  from the api access view.

Conflicts:
	docs/pithos-api-guide.rst

Add script snf-register-components and helper snf-service-export.

commit:8a0c7040367761cd5d5383ac53dfe1c0161c1d02
has restricted the X-Object-Public exposure
in container detailed list requests
only to the object owner and if public parameter is supplied.
Now we have weaken this requirement so this information
is returned only to the object owner regardless of
the public parameter existence.
The pithos api guide has been updated also appropriately.