/Provision API

[Ben-Hodgkiss]

Overview

Following the Pipeline API workshop day, we have now identified and prioritised the different APIs that are required to remove the Providers team dependency on datasette.

This ticket is to create the /provision API. At the workshop, we identified the following criteria for this that can be found on this Google sheet.

Method	GET
Path	/provision

Inputs

Required	Optional
	organisation
	dataset

Outputs

Existing	New
organisation	provision_reason
organisation_name
dataset
active_endpoint_count
error_endpoint_count

Datasette Tables

provision_summary

Tech Approach

To be completed during Refinement.

Acceptance Criteria

• [] API created to query on the Provision table
• [] Queries can filter on organisation and dataset
• [] Output includes organisation, organisation_name, dataset, active_endpoint_count and error_endpoint_count

Resourcing & Dependencies

• Developer to attend the Providers Stand-Up on Tuesdays and Thursdays (they do not need to attend the Infra Stand-Up on these days).
• Providers to offer support including pair programming and PR reviewing.

[eveleighoj]

The provision table is an output of the specification data. In order to tackle this we'll need to consider publishing the generated specification to s3 into a bucket for the API to access. We'll likely need to do this for a few things but. think about the approach.

Counts are mentioned above, counts are not present on the normal provsion table so I'd assume it's a different provision summary table?