Skip to content

tag schema versions #7224

@n1ru4l

Description

@n1ru4l

Today we always only serve the latest schema version artifacts from the CDN from the following URL:

https://cdn.graphql-hive.com/artifacts/v1/<target-id>/supergraph
https://cdn.graphql-hive.com/artifacts/v1/<target-id>/sdl
https://cdn.graphql-hive.com/artifacts/v1/<target-id>/services

We can introduce tagging to give more control over which schema version is served to a specific router/gateway instance

A tag would be applied via the Hive CLI (and/or an API call and/or Dashboard UI).
The state of the tag would then be stored on our end in the database, so we can show which tag is the latest schema version and also quickly retrieve the schema version for a specific tag.

Image

On the CDN side, the artifacts would then be accessible via the a URL similar to this:

https://cdn.graphql-hive.com/artifacts/v1/<target-id>/tags/<tag>/supergraph
https://cdn.graphql-hive.com/artifacts/v1/<target-id>/tags/<tag>/sdl
https://cdn.graphql-hive.com/artifacts/v1/<target-id>/tags/<tag>/services

Related issues:

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request that adds new things or value to Hiveneeds-customer

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions