Extend provisioning to support collections at a project level

[stuartc]

Background

Lightning’s Project Spec documentation outlines how to define and manage resources in a project.yaml file. However, we currently have no way to define Collections in the spec. Collections can be accessed (but not created) via the CLI (see docs), and we’d like to add this functionality to our project.yaml so that everything can be configured in one place.

# project.yaml
name: MyProject
collections:
  - name: my-first-collection

or

# project.yaml
name: MyProject
collections:
  - my-first-collection
  # this is shorthand for name: my-first-collection

Requirement

Extend the current provisioning API to handle a collections key on the root of the document. Parsing, validating and create/update/deleting collections in the same way other entities are handled.

Open questions

Do we care about permissions? Can anyone who can create/update a workflow also create/delete a collection?