registry
registry copied to clipboard
apigee
The Registry API allows teams to track and manage machine-readable descriptions of APIs.
The benchmark tests can be used against any running registry service To run it against a local running service you can run ``` source auth/LOCAL.sh export REGISTRY_PROJECT_IDENTIFIER=bench apg admin create-project...
The [codecov.io report](https://app.codecov.io/gh/apigee/registry) shows very low coverage. Determine if this report is correct - if it is incorrect, correct the report or remove the README badge. If the report is...
https://github.com/golang-standards/project-layout
As mentioned here #631, we may want to consider integrating benchmarking tracking into our builds. (For example: https://github.com/marketplace/actions/continuous-benchmarking-for-go)
As suggested [here](https://github.com/apigee/registry/pull/610#discussion_r905258254), let's consider how [embedded-postgres](https://github.com/fergusstrange/embedded-postgres) might simplify server tests and CI.
Resolve [this TODO](https://github.com/apigee/registry/blob/4701f382dd2bfcaf8aeb238556703b1bb6ff44df/server/registry/actions_projects.go#L171) and similar ones in the api and version update handers.
The README mentions tests/demo/walkthrough.sh as a demonstration of the API, but we aren't currently verifying that the script works with new commits. It seems unlikely that we would break it...
Currently imported YAML files can refer to tagged specs in deployment records [here](https://github.com/apigee/registry/blob/67f42553312cf971a5314a24929c861d893603bb/cmd/registry/cmd/apply/testdata/sample/apis/registry.yaml#L48) but there is no way to associate tags with specs as they are being imported in YAML....
Currently these two methods in the API require an explicit reference to a revision of the spec or deployment to be tagged -- i.e. the revision id must be included....