💅  Service Config Formatting

• We improved how your service config is shown in the dashboard. We’re now formatting it with singles quotes and trailing commas.

📚 Importing functions from the stellate package

You can now import functions from the stellate package in the UI, fully type safe 🎉 

More Fixes

• The CLI is now printing a correct config for the stellate init command.
• The dashboard now shows the billing portal for failed payments.
• Links to individual Canny posts are fixed.
• Our Slack integration authentication had a hick up, which we now fixed.
• We fixed some edge cases in the configuration function serialization, which caused errors or bundled them into a faulty code.
• The rules in the configuration now support null and undefined rules. This is particularly helpful if you want to calculate the rules programmatically.
• Ensure that all responses are purgeable, even in cases where we run a pass-through (bail), with the origin setting a cache control header.

We are excited to announce that our GraphQL API is now open for anyone to use! 🎉

GraphQL gives a lot of power to developers through flexibility, which is why many of us love it. That flexibility has the downside of making it harder to open up GraphQL APIs, with authorization, schema evolution and security being non-trivial concerns.

However, opening up your API and enabling third-party developers to integrate with your systems is a powerful way to create business value. That’s why our current mission to make open GraphQL APIs ubiquitous, and our first step towards that is opening up our own GraphQL API to allow anyone to build an integration with our platform.

If your company is using GraphQL and you’re also thinking about opening up your GraphQL API, apply to be a part of our Open GraphQL API Pilot Program, where our GraphQL experts help companies successfully open up their GraphQL APIs.

Learn more in the announcement blog post and check out the docs to get started!

Team

• Dominic Petrick, who previously worked on the Prisma Query Engine, has joined us as a full-time Rust developer

Changes

• All Stellate endpoints now show the new GraphiQL v2 🎉 To see an example, visit graph.stellate.co 
  • If you're not seeing this at your Stellate service's endpoint, make sure to enable introspection and set enablePlayground: true
• Changelog inception: the changelog has been embedded in the dashboard sidebar so you all can see this
• We now allow overwriting enablePlayground within environments
• We added two new mutations to our open API:
  • applyForJob - apply to a job at Stellate through a GraphQL mutation 🤯
  • submitApiFeedback - GraphQL inception: making it possible to give feedback for our new API through our API 😍

Fixes

• Fixed a rare infinite loop when closing modals, which sometimes triggered an infinite toast popup loop
• Incorrect variables are now handled gracefully in GraphiQL
• Fixed Intercom authentication so we know it's you reaching out with questions
• Fixed an issue with upgrading to the business plan
• Fixed showing empty cards in the service history
• Fixed the error query and country not showing
• Ensured the cache state & response timing is always visible in GraphiQL
• Fixed the Purging IDE button and shared metrics layout

Last week, we announced five new major features! Let’s recap.

A whole new dashboard

You gave us the feedback, we listened! We shipped a whole new dashboard with new metrics, purging history and much more. Check it out at stellate.co/app

New GraphQL Metrics

With the new dashboard, we released brand-new GraphQL Metrics that allow you to slice and dice aggregate traffic data, understand individual requests in full context, and monitor performance and errors.

Purging Analytics

The new purging analytics allow you to have full visibility into your cache's activity, which allows you to optimize your cache hit rate and have the confidence that no stale data is served to your users.

New GraphiQL integration

We integrated a GraphQL IDE into our new dashboard to allow users to test queries against their API quickly. The IDE is based on the upcoming new version of GraphiQL, which is more extensible and customizable.

Universal Configuration-As-Code

The new Stellate dashboard includes a code editor for "universal configuration-as-code." This allows for better knowledge transfer between UI and terminal, instant feature parity and faster shipping, and DRY code reuse across environments. We are exploring ways to further utilize UI to enhance the experience with the new TypeScript-based configuration.

Since then, we got a lot of great feedback and worked on the following fixes:

Changes

• Introduce pagination for the Service History
• Show config diff in --dry command

Fixes

• Fix the chat bubble in the dashboard
• Fix the top navigation moving and shifting when activating different items
• Fix tracking the PASS response state and visualizing it in GraphiQL
• More robust config validation in the UI
• Improve dashboard UX by adding stand-in values for the navigation
• Fix submitting the query depth limit
• Replace @monaco-editor/react with our own implementation, which increases the reliability and performance of the code editor in the dashboard

The GraphCDN team spent the last week in Lisbon, Portugal at an amazing onsite. (Since we are a distributed company, we're actually "on-site" when we're all together. 😊) Other than getting to know each one of us better, and working hard on the vision and mission for our company, we also shipped some improvements, fixes, and new features.

New

• We have a new field called servicesList on the organization type, which allows you to paginate/filter through all services owned by an organization. This implements the relay-pagination spec.
• POST requests with an empty body are now blocked at the edge.

Improved

• The Forwarded headers are now appended rather than replaced
• Requests are retried at most once to not overload your backend services.

Fixed

• We have fixed the Slack channel selector, which was not working for Slack workspaces with more than 1000 channels. We will now load all non-archived channels when loading the page. Unfortunately Slack does not implement filtering via their API 😅, which makes our UI and background logic a slight bit more complicated.
• We now make a better attempt at removing the TLS subscription when removing a custom domain from your service.
• We have fixed an issue where we would cache empty array root-fields

New

• Set Forwarded and X-Forwarded-For headers via GraphCDN edge workers.
• The GraphCDN CLI serve command now exposes a Purging API in addition to your cached GraphQL API in version 1.11.0
• Added a list of 3rd party subprocessors that GraphCDN uses at https://graphcdn.io/subprocessors.pdf

Fixed

• [Private Beta] If GraphCDN encounters an invalid JWT, requests will be passed on to your backend service instead of being treated like an unscoped request.

We are also working on a new version of our dashboard and shipped some internal improvements and prerequisites for that. See https://twitter.com/mxstbr/status/1516784404777123851 for a sneak peek.

When you run the graphcdn push command we immediately validate your configuration file to ensure it is correctly formatted.

However, the validation error messages were not as helpful as they should be. We have overhauled them in the latest release of the CLI (v0.4.3) to make sure they precisely explain the issue(s):

$ graphcdn push
Error:  Invalid graphcdn.yml:
- schema: Required
- defaultCacheControl.scope: Expected string, received number

Install the latest version of the CLI by running the npm install graphcdn@latest command in your project's directory.

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!

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!