The signer should be whatever we're using for sts / preloads / etc. The schema, initially, could look something like this: We need to be able to support attachments. { "type": "object", "description": "Certificate revocation data.", "additionalProperties": false, "properties": { "details": { "type": "object", "title": "Details", "required": [ "name" ], "properties": { "name": { "type": "string", "title": "Name" } } }, "id": { "type": "string", "title": "Id", "description": "Record id." }, "schema": { "type": "integer", "title": "Schema version", "description": "Schema version." }, "incremental": { "type": "boolean", "title": "incremental", "description": "Is this an incremental update (false if a new cascade, true for updates)." }, }, "title": "Revocation Data", "required": [ "incremental", ] }

Ping ... I'd like to try to post a test attachment to this collection ASAP.

What would be the name of this collection? cert-revocations? Should the editors and reviewers be the same as those of the intermediates collection?

Created https://github.com/mozilla-services/cloudops-deployment/pull/2005

(In reply to Mathieu Leplatre (:leplatrem) from comment #2) > What would be the name of this collection? cert-revocations? Perfect, thanks. > Should the editors and reviewers be the same as those of the intermediates > collection? Yes.

PR on cloudops is ready to be deployed.

For the next one, I added instructions on the Mana page, it should be more efficient ;) https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=66655528

Done :) Thanks Wei!

https://github.com/mozilla-services/cloudops-deployment/pull/2005 merged and deployed to -prod along with kinto-dist v7.1.0.