0.9.0

Kinto

kinto 3.3.2 → 4.3.0: https://github.com/Kinto/kinto/releases/tag/4.3.0

Highlights

• Redis backends were dropped from core, and are now packaged separately in
  kinto-redis
• New /__version__ endpoint which reads a version.json file to expose what version
  has been deployed. Its location can be specified in the kinto.version_json_path
  setting (fixes #830)
• New built-in plugin kinto.plugins.history to track history of changes per bucket
  from the Kinto Admin UI (*must be added explicity in the kinto.includes setting)
• kinto migrate now accepts a --dry-run option which details the operations
  to be made without executing them.
• New built-in plugin `kinto.plugins.quotas``to set storage quotas per bucket/collection
  (c.f. Web Extensions storage)
• The history and quotas plugins execution time is now monitored on StatsD
  (kinto.plugins.quotas and kinto.plugins.history) (#832)
• The permissions attribute is now empty in the response if the user has not
  the permission to write on the object (Kinto/kinto#123)
• Parent attributes are now readable if children creation is allowed (Kinto/kinto#803)
• New kinto delete-collection command to delete a collection from the command-line.

kinto-admin

kinto-admin 1.3.0: https://github.com/Kinto/kinto-admin/releases/tag/v1.3.0

• Add views for browsing a collection history (#196)
• Updated kinto-http to v2.3.0.
• Activate the signoff plugin to allow triggering a signature from the Admin.

kinto-signer

kinto-signer 0.7.3 → 0.9.1: https://github.com/Kinto/kinto-signer/releases/tag/0.9.0

The API can now optionally rely on a workflow and can check that users changing collection status
belong to some groups (e.g. editors, reviewers). With that feature enabled,
the signature of the collection will have to follow this workflow:

• an editor will request a review by setting the collection status to to-review;
• a preview collection will be updated and signed so that QA can validate the changes
  on the client side;
• a reviewer — different from the last editor — will trigger the signature by setting
  the status to to-sign as before.

In order to enable this feature, the following procedure must be followed:

• Change the resources settings to add a preview collection URL ({source};{preview};{destination})

    kinto.signer.resources =
      /buckets/staging/collections/certificates;/buckets/preview/collections/certificates;/buckets/blocklists/collections/certificates

• Enable the review and group check features:

    kinto.signer.to_review_enabled = true
    kinto.signer.group_check_enabled = true

• Last, create editors and reviewers groups in the staging bucket, and
  add appropriate usernames to it. The groups can now be managed from the
  Kinto Admin UI. Otherwise via the command-line:

    $ echo '{"data": {"members": ["ldap:some@one.com"]}}' | \
        http PUT $SERVER_URL/buckets/staging/groups/editors --auth="admin:token"


    $ echo '{"data": {"members": ["ldap:some@one.com"]}}' | \
        http PUT $SERVER_URL/buckets/staging/groups/editors --auth="admin:token"