Stellate Product Updates logo
Back to Homepage Subscribe to Updates

Product Updates

See the latest new features, improvements, and product updates

Labels

  • All Posts
  • Fix
  • Announcement
  • Improvement
  • graph api
  • feature

Jump to Month

  • December 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • January 2023
  • September 2022
  • August 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
Announcement
4 years ago

Organizations

Open your GraphCDN dashboard and you will see something new: organizations. They allow you to group multiple services under one umbrella with consistent access control, billing and management.

We have automatically created organizations for all of your services, but you can of course also create a new one for your company specifically:

Screenshot 2021-05-28 at 12



Avatar of authorMarko Locher
Improvement
4 years ago

Configure your cache with rules

Instead of the old, tedious way to configure caching per GraphQL type or field, we now have cache rules!

Head over to the "Rules" tab in your service's dashboard and you will see your first rules already:

Screenshot 2021-05-26 at 14

To upgrade your graphcdn.yml, simply run graphcdn pull and we will automagically rewrite your cache configuration into the new rules!

Avatar of authorMarko Locher
Fix
4 years ago

Support schemas with custom root type names

Some GraphQL APIs rename the root type names from the standard "Query", "Mutation" and "Subscription" to something else like:

schema MySchema {
  query: RootQuery
  mutation: RootMutation
  subscription: RootSubscription
}

We now handle this case well in the UI, showing you "RootQuery" instead of relying on the standard root type names!

Avatar of authorMarko Locher
Announcement
4 years ago

Show docs on the website

Rather than linking out to Notion, our docs are now on the website at https://graphcdn.io/docs! 🎉

Screenshot 2021-05-28 at 12


Avatar of authorMarko Locher
Announcement
4 years ago

CLI flow to create services

You can now create services from the CLI by running a single command and answering a handful of questions:

$ npm init graphcdn
# or if you're using yarn
$ yarn create graphcdn

This will do everything you need to do to get started with GraphCDN: 

  1. Install the graphcdn CLI
  2. Create a graphcdn.yml file
  3. Push it to GraphCDN.
Avatar of authorMarko Locher
Announcement
4 years ago

Custom domain support

One of our most highly requested features just landed: custom domain support! You can now assign a custom domain to your service, which can be used instead of your .graphcdn.app URL. This is particularly useful if your users authenticate with cookies.

Head to your service's settings, enter your preferred custom domain and follow the instructions to set the correct DNS records: 

Screenshot 2021-05-27 at 17


Avatar of authorMarko Locher
Improvement
4 years ago

New Admin API URLs

The Admin API, which you use to purge data, has moved to a new location in order for us to make it even faster. Moving to the new location should take a handful of minutes at most: The only thing you have to do is change the URL you send requests to: instead of https://graphcdn.io/api/management/[name], send them to https://admin.graphcdn.io/[name]. That's it!

We'll keep the old path around for two months and will notify any customers still using it in a month directly.

Avatar of authorMarko Locher
Fix
4 years ago

Cache private results for public users

We had a bug where any query that had a scope set would not be cached at all for public users.

While the cache for public users should not be shared with authenticated users in that case, the query should still be cached for them. We've now resolved those issues and the caching works as it should again!

Avatar of authorMarko Locher
Announcement
4 years ago

Automatic mutation invalidation

We've been dreaming of this feature ever since we first started building GraphCDN so we're very excited it's finally here!

How it works

Let's say you have a query cached that looks like this:
{
  "user": {
    "id": 5,
    "name": "Peter Pan"
  }
}
and run a mutation that edits that user's data, something like:
mutation {
  editUser(id: 5, name: "Saint Peter") {
    id
    name
  }
}
As soon as the mutation completes, GraphCDN will fully automatically invalidate all cached queries globally that contain that user's data. You don't have to implement manual caching for any data changes that happen via GraphQL mutations anymore!
Avatar of authorMarko Locher
Fix
4 years ago

Fix CORS for requests with credentials

For requests that set "credentials": "include" we were incorrectly returning the Access-Control-Allow-Origin header set to the wildcard *, breaking those requests.
We just rolled out a fix for this by properly responding with the matching Origin request header instead!
Avatar of authorMarko Locher