registry
registry copied to clipboard
apigee
The Registry API allows teams to track and manage machine-readable descriptions of APIs.
Many of the Registry tool [commands](https://github.com/apigee/registry/tree/main/cmd/registry/cmd) have incorrect or missing input validation. For example, issue #472 describes a bug that causes a lack of flag validation. Other commands [require a...
Users can define manifests with generated resources that collide with existing non-generated resources. For example, the registry could have specs with ID `openapi.yaml` that were added manually, then a manifest...
Running the bulk upload commands without specifying a project ID will proceed without error until it attempts to use the project ID in a request to the server. Failing to...
Currently the names package includes representations of project names and API names, but in between these names, there are location entities that are not represented. Location support was added after...
Hey all, One of the first items we would be layering on top of the registry is automatically scraping from existing data sources of api's, this could include apigee, kong,...
The Registry tool may be able to leverage the [postmanlabs/openapi-to-postman](https://github.com/postmanlabs/openapi-to-postman) library to export OpenAPI v3 specs as Postman collections. Below are some suggestions for how this feature might be offered....
We do not currently understand the behavior of the Registry API under heavy load. Commands such as spec bulk uploading currently produce the largest loads against the API. The addition...
A registry of Protocol Buffer-based APIs may have some requirements that aren't shared with other API styles. These could include: - Avoiding conflicts by ensuring that all messages and rpc...
With [gRPC compression](https://grpc.github.io/grpc/core/md_doc_compression.html), we may be able to eliminate any need to compress specs before uploading them, moving compression into the gRPC API client. This would need to be supported...
Currently, the `registry compute lint ... --linter=aip` command, implements a workaround where it is cloning two repositories https://github.com/googleapis/api-common-protos https://github.com/googleapis/googleapis Investigate how the linter executes, and evaluate the need for git...
