The Stellate CLI allows you to configure your Stellate service via configuration-as-code. It can both pull the currently active configuration from the Stellate web app, as well as (selectively) push configuration from your local YAML file to the Stellate web app. It is a great way to make sure you have a backup of your configuration at hand and can follow (and approve) changes made. We recommend using your CI workflow to push changes to your Stellate configuration.
See the CLI documentation for how to install and use the Stellate CLI.
- ⚠️ Fix login crash when the server returns nothing
- Correct dashboard URL
- Allow the user to override
environmentssection of the stellate-config
- Show config diff when pushing and add the
- Guard against crashing when computing the configuration diff
- Send source when pushing configs or schemas. This was previously only sent in CI
- Change links to dashboard printed in CLI outputs
- ⚠️ Fix commands formatting in README
- Rename CHANGELOG from GraphCDN to Stellate
- Allow users to specify the config output format
mutationPolicycorrectly, added because of bumping of the
- ⚠️ Fix issue where the types of
@gcdn/configurationare not inlined
- Allow for code-based configuration files
- Add the
mutationPoliciesoption, which allows consumers to specify how the automatic invalidation should work
- [Beta] Added a new
graphcdn checkcommand to check for breaking changes. See the CLI documentation for more information.
- We fixed an issue that removed response headers on
- Make the Purging API locally as well. The CLI will now print both, the URL for the GraphCDN backed GraphQL API, as well as the URL for the Purging API connected to your development service at startup.
- Upgraded to graphql v16.3.0
- Fix issue where path is translated to
/undefinedand add debounces on reconnect
- Moved a GraphCDN internal dependency to a development dependency
- Updated the included dependencies to their latest respective versions
- Re-implement the
graphcdn servecommand to use a websocket to facilitate communication between GraphCDNs edge locations and your local development environment. This will improve compatibility with existing infrastructure and solve some issues users where experiencing.
- Fix a bug that redirected login (and similar commands) to the wrong subdomain on the GraphCDN website.
- Fix a bug that caused errors on pushing configuration changes with the error message Expected signal to be an instanceof AbortSignal.
- Add the option to only push the schema of your API to GraphCDN. This option is added via the
graphcdn push schemasubcommand. It will ignore the rest of your configuration and exclusively push new schema or introspection information.
- Added the
--orgoption to the
servecommand in case users leverage this command in a non-interactive environment like Docker.
- Fixed a bug where the CLI would crash on missing the root
- Fixed a bug that would post outdated configuration in
- Added support for Bypass Headers.
- Updated documentation links to point to https://docs.graphcdn.io/docs/cli.
- Changed the license of the GraphCDN CLI to the MIT license. License information is shown on the npm package page.
- Improved various error, warning and notification messages used throughout the CLI.
- Added the
-o) option to specify which organization should be used when pushing configuration to GraphCDN
- Removed the requirement for the
schemafield when pushing configuration to a GraphCDN service.
- Upgraded to Next.js 12.
- Fixed an error where
graphcdn pullwould not write the service name into the pulled configuration file.
- Upgraded dependencies and cleaned up some internal dependencies.
- Download ngrok on demand (required for the
- Updated the CLI to use new internal configuration and validation packages.