Add support for recommended_deployment fields and automatically uncompress gzipped artifacts

This release includes two bug fixes that fix gaps between the API specification and implementation.

• #459 ensures that the recommended_deployment field of APIs is stored and returned as specified in the API protos.
• #457 ensures that artifacts stored with gzip compression (as noted in their mime types) are automatically decompressed by the handler of the GetContents method as described [in the API protos].(https://github.com/apigee/registry/blob/61c5bc7df3a3ddbdb9587ae184b5d26a2931b39e/google/cloud/apigeeregistry/v1/registry_service.proto#L328).

Additionally in the registry-server,

• #461 contains a database performance improvement contributed by @maghasemzadeh.

On the client side,

• #458 adds missing support for setting labels and annotations on Deployment resources using the registry tool.
• #456 causes generated clients to automatically retry DeadlineExceeded gRPC errors.

Improved error reporting + small improvements and bug fixes

This release adds additional error reporting to the server core to better support retry of transient error conditions.

Other additions/changes include:

• AIP-135 compliant support for cascading deletion
• new Admin service GetStorage method that returns database summary information
• an addition to the Admin GetStatus method that returns build information
• correction of an incorrect type annotation for new ApiDeployment message
• a fix for a bug that caused artifact "blobs" associated with ApiDeployments to leak

This release adds a column to the artifacts database table and requires a database migration. This can be done by calling the MigateDatabase method in the Admin service after the Registry service has been upgraded.

Private Preview

List deployment artifacts (#404)

* Add support for listing deployment artifacts.
* Only create deployment artifacts if the deployment exists.
* Update TestCreateArtifactResponseCodes to seed "grandparent" resource.

Database migration, improved bulk uploads of Google APIs

• Adds a new MigrateDatabase method to the Admin service that auto-migrates the Registry backend database.
• Refines registry upload bulk protos and registry upload bulk discovery to better align with Google API practices.

Deployments resources, allow_missing in all update methods

This makes two API-level changes:

• adding a new Deployments resource for tracking API deployments (addressing #198)
• adding allow_missing fields to update request methods to allow "upsert" operations as described in AIP-134.

Deployments service protos, improved resource name parsing

This adds protos for a currently-unimplemented resource that models deployments of APIs. Clients can be written to call these methods but they will return gRPC UNIMPLEMENTED status codes (for now).

We've also changed the names package in server/registry/names, hiding the regular expressions for resources and recommending use of functions named Parse<ResourceType> and Parse<ResourceType>Collection to validate resource names and extract their components. This is a breaking change for client code that uses the names package.

Admin service

Admin-only APIs (GetStatus and Project-related methods) are now in a separate Admin service.

This improves consistency between the Registry service defined in this repo and future hosted versions.

SQL-only, new methods for accessing spec and artifact contents

This release exclusively supports SQL-based backends (Postgres, SQLite) and includes some changes to the spec and artifact accessors that allow them to be downloaded directly using transcoded gRPC requests. For example, the contents of an API spec can be downloaded with

curl $service/v1/projects/disco/apis/translate/versions/v3/specs/discovery.json/contents

Testing and AIP compliance improvements

This adds significant new tests that verify core API features and aspects of the API that are determined by AIPs. This will be the last release with support for the Cloud Datastore API - soon we will focus our implementation on SQL backends through a gorm interface.

Registry API v1

This updates the Registry API to v1, reviewed and approved by Google's API governance team for improved consistency with Google's Cloud and Kubernetes APIs.