registry
registry copied to clipboard
The Registry API allows teams to track and manage machine-readable descriptions of APIs.
### Expected Behavior Resources should be case insensitive after creation as described in #91. ### Current Behavior Resources can be saved to the database without their identifiers being fully normalized....
### Expected Behavior Creating a resource should only be one `INSERT` query. ### Current Behavior Before the `INSERT` query that successfully creates the resource, there is an `UPDATE` query that...
The Registry API design follows the Google Cloud pattern for allowing labels on resources that is described in [Creating and Managing Labels](https://cloud.google.com/resource-manager/docs/creating-managing-labels). To avoid future compatibility problems, we should verify...
Request: ``` curl --request POST 'http://x.x.x.x/v1/projects/x/apis/my-api/versions/v1/specs/proto@2d63042a:tagRevision' \ --header 'Content-Type: application/json' \ --data-raw '{ "tag": "tagME" }' ``` Response: ``` { "name": "projects/x/apis/my-api/versions/v1/specs/proto@tagME", "filename": "", "description": "", "revisionId": "2d63042a", "mimeType": "",...
At the moment the `ListApisRequest` supports pagination and filtering, however if the endpoint is to be used to supply data for most common paginated usecases (i.e. UI tables) the request...
There's at least [one race condition](https://github.com/apigee/registry/pull/379#discussion_r741546190) in our update operations that we've addressed for single-process servers but which we expect will still appear when we run multiple parallel instances of...
We tripped up in #277 and would have caught it earlier if CI or other tests were verifying our HTTP transcoding configuration. This would require setting up an envoy proxy...
### Background Most of our API methods perform several database operations. For example, the `UpdateApi` method reads the API first to make sure it exists and to load its current...
With our current use of `exec.Command` there is no direct way to write unit tests. We have some functional tests which execute real shell commands, but we are limited here...
Starting with version 6.X, spectral expects a required `--ruleset` argument, to pass a [ruleset](https://meta.stoplight.io/docs/spectral/ZG9jOjYyMDc0NA-rulesets) file for linting. It should be possible construct this ruleset file from the `rules` configured in...