registry
registry copied to clipboard
apigee
The Registry API allows teams to track and manage machine-readable descriptions of APIs.
The server currently exits with an error if it is unable to make a database connection. I've seen this cause problems in two situations so far, both associated with running...
After some highly concurrent load tests, I've noticed that the server is starved for connections. Would it help to adjust our pool configuration? https://go.dev/doc/database/manage-connections https://github.com/GoogleCloudPlatform/golang-samples/blob/66716d85a55616601c8a0b634885505f7a439a49/cloudsql/postgres/database-sql/cloudsql.go#L178 https://cloud.google.com/sql/docs/postgres/manage-connections#go_2 https://cloud.google.com/sql/docs/quotas#postgresql
I think our default GAPIC retry configuration might be too aggressive. With an initial retry interval of 0.2s, connections are retried quickly and for large bulk uploads and controller jobs,...
Several issues (#623, #448, #382) raise concerns about the lack of transactionality in mutating action handlers. A few different solutions are suggested, including table-level locking (to me this seems overly...
Styleguides currently support only `mime_type` filters to decide the target resource. Add support for a combination of `pattern` + `filter` the way we support in scores [example](https://github.com/apigee/registry/blob/main/google/cloud/apigeeregistry/v1/scoring/definition.proto#L79)
The rules used by the registry check command that validates the contents of the resource files are currently hard coded. I would like to add custom checks to ensure that...
When PubSub notifications are enabled and the `registry-events` topic already exists in the given project, the registry server fails to startup with the following error: >FATAL[0001] Failed to create registry...
Follow-up from an earlier [YAML storage PR](https://github.com/apigee/registry/issues/1181#issuecomment-1579601151): ``` --- FAIL: TestConformance (0.19s) --- FAIL: TestConformance/normal_case (0.05s) conformance_test.go:465: Failed getting artifact contents projects/conformance-test/locations/global/apis/petstore/versions/1.0.0/specs/openapi/artifacts/conformance-openapitest: rpc error: code = NotFound desc = "projects/conformance-test/locations/global/apis/petstore/versions/1.0.0/specs/openapi/artifacts/conformance-openapitest"...
Hey, regarding specs, it says that specs shouldn't be inlined but there's no reference example of how a Spec should be formatted. it would be good to have a copy-paste...
