It would be very useful to define something like like for invalidating lists: "when x mutation is made, invalidate a,b & c list(s) where auth and/or other header(s) match that of the mutation."

You show errors but it's hard to know what the errors are and why they're happening to debug them

I'd like to monetize my GraphQL API and have Stellate take care of as much as possible in this process. That includes the metrics to know how much a user of my API used the API.

Create API documentation using AI

We're currently using Apollo Server caching, where you decorate your schema with @cacheControl directives. Context: https://www.apollographql.com/docs/apollo-server/performance/caching/ Since we're already using it throughout our large schema, it would be nice if it was offered so we can keep the rules with the types definitions and not need to recreate a config to migrate from that to this

We use Hasura subscriptions extensively, how can users still send us subscription requests after we move to GraphCDN?

If this sounds true to you, then please upvote: "I want to bring my own authentication system and integrate that with the Stellate GraphQL Developer Portal"

In some cases, the authenticated data is subject related and when a new token is being issued for the user, the token is supposed to belong to the same user. For now it's not possible to validate an asymetric authorization token on GraphCDN side because it'd require to use the issuer public keys endpoint (e.g.: https://id.acme.com/.well-known/jwks.json ). Having the ability to configure such endpoint from GraphCDN's end would permit to validate dynamically tokens while leveraging the cache benefits.

This would allow people to use PagerDuty to get notified when an alert triggers.