datacenter
is the primary key and here acts as a forigen key
for namespaces.
datacenter
is the primary key and here acts as a forigen key
for namespaces. We never want two datacenters with the same name.
Use cases exist for fetching a single, discrete revision of a blueprint and also generically fetching whatever the latest might be.
Use cases exist for fetching a single, discrete revision of a blueprint and also generically fetching whatever the latest might be. In this way, we funnel all that through a single function that either uses a different constraint to get a single record, or in the latter case, sorts by descending revision and picks the head record.
Given a deployment ID, find all the associated gubbins.
Fetch a single repository based on the supplied slug.
This will first try to find a traffic shift, if none is found, it will try to find the latest matching deployment
Does what it says on the function.
Given a set of repositories, associate them with a specific user.
Given a set of repositories, associate them with a specific user. This is used when we are syncing repositories at the behence of a user.
Fetches the latest blueprint revision for every known blueprint.
Fetches the latest blueprint revision for every known blueprint. The idea here is to provide insight into what blueprints exist in the system; given we have the inspection API for checking specific revisions, simply showing what's available and a pointer to the latest revision, should be informative enough.
Fetch all repositories for a given user.
List all the repositories the user has access too that have webhooks enabled.
Fetch all repositories for a given owner, that the specified user has access too.