v0.6.8
registry apply improvements
This release fixes what was probably the most annoying problem with registry apply: because deployments expect to point to spec revisions, and spec revision ids aren't known until they are created, it was impossible to create a spec and a deployment that referenced it in a single YAML file.
This fixes that by observing that when we apply YAML files, we create specs before we create deployments, so deployment YAML can be written to point to a spec (without a revision ID) and when it is applied, registry apply will just get and use the latest revision of that spec. So now we can apply YAML files that look like this:
apiVersion: apigeeregistry/v1
kind: API
metadata:
name: registry
data:
displayName: Apigee Registry API
versions:
- metadata:
name: v1
data:
displayName: v1
specs:
- metadata:
name: openapi
data:
filename: openapi.yaml
description: OpenAPI description of the Registry API
mimeType: application/x.openapi+gzip;version=3
sourceURI: https://raw.githubusercontent.com/apigee/registry/main/openapi.yaml
deployments:
- metadata:
name: prod
data:
apiSpecRevision: v1/specs/openapi
endpointURI: https://apigeeregistry.googleapis.com
Note that the apiSpecRevision field just points to a spec and registry apply will automatically look up the revision to use (and if a revision ID is included, we will continue to use that).
We also inadvertently broke the --version flag in v0.6.7. That is fixed now.
~/.registry/bin$ ./registry --version
registry version v0.6.8