Scheduled execution for edge functions, key-value stores you can share between projects, a per-domain metrics page, search index browsing, and version 5 of the CLI and deploy action.
A new metrics page shows traffic, cache, response status and origin status metrics for all of a project's domains or for a single domain you select. You can view the last hour by minute, the last month by day or the last year by month, with charts for requests, bandwidth, cache hit ratio and origin offload over time.
New Edge functions
Scheduled execution
You can now run an edge function on a recurring schedule. Pick a preset such as every hour or the first day of every month, or build a cron expression with the built-in schedule builder. Each schedule sets the HTTP method (GET, POST, PUT or DELETE) and can send custom request headers and payload data to the function. A history view records each run with its status code and response body, so you can review past executions and debug behaviour over time. A new guide in the documentation covers schedule and request configuration.
Custom search extractor sets now support three new options: fixed values, friendly admin titles and wildcard matching on URL patterns. An extractor set uses XPath selectors to copy content from the pages that match a URL pattern or content type into fields of their search records. A fixed value puts the same text in a field for every matched page, and the title names the set in the dashboard list. You can preview an extractor against your content before you save it. If an XPath selector is not valid, the preview reports it clearly.
New Search
View and filter search index items
The search page in the dashboard has a new View index items option that lists the records in your project's search index. You can filter the records by keyword and page through the results, so you can confirm what has been indexed without leaving the dashboard.
Edge function, filter, and auth function deployment
Version 5 of the CLI is published only as the quantcdn/cli Docker image, not on npm. It adds function, filter and auth commands, which deploy an edge function, content filter or auth function from a file. It also adds a functions command, which deploys several of them at once from a JSON configuration file. The unpublish stage of a deployment now runs more operations in parallel, so it finishes faster.
Version 5 also offers an interactive mode, and the CLI can run fully non-interactively when all required parameters are supplied. The active configuration is shown on every run. The scan command is significantly faster through batched metadata queries and now updates the local revision log as it runs.
Improved CLI
Soft purging
Version 5 can also perform soft purges, which mark content as stale instead of deleting it from edge caches.
Crawler configurations with no page limit now show "Unlimited" instead of a raw value, so unbounded crawls are easy to spot.
Improved Edge functions
Content filters on proxied 404 responses
Content filters now also apply to HTML pages that a proxy on 404 rule fetches from your origin. A proxy on 404 rule is a proxy rule with "Only on 404" selected, which sends a request to your origin only when Quant has no content for the path. Filtered markup is now the same whether Quant or your origin serves the page. Proxy on 404 also changes: when Quant does not hold the exact URL of a request, the request now goes straight to your origin. For example, a page URL with an added query string now goes to your origin. Before, Quant removed the query string or trailing slash and served its own copy of the page.
Improved Edge functions
Auth function guide and examples
Auth functions, introduced in September, are now covered by a new documentation guide. It explains how an auth function lets a request continue, how to apply it to paths with an Edge auth rule and how to chain several auth functions. The prebuilt examples in the code editor now also include sign-in with Azure AD, Facebook and GitHub, alongside Apple, Auth0 and basic authentication.
Webform submission views now render nested and structured values correctly instead of flattening them, so multi-value and complex fields are readable in the dashboard.
Improved GitHub Actions
Deploy action v5 with edge function deployment
Version 5 of the deploy action runs on version 5 of the Quant CLI. A new functions input takes a JSON file listing your edge functions, content filters and auth functions, so one workflow can deploy them with your static assets. The attachments input is removed.
Remove the attachments input from your workflow when you upgrade to version 5 of the deploy action.
Key-value stores, introduced in September, can now be linked to other projects in your organisation. Select Link to Project on the KV stores page and choose a project, and edge functions in that project can read and write the same store. The store then appears in that project's own KV store list with a Linked badge.
A new documentation guide covers key-value stores. It walks through creating a store and managing its items in the dashboard, and shows how an edge function stores, reads and deletes values, with JavaScript objects encoded and decoded as JSON automatically.
The Go admin client now includes methods for the key-value store endpoints added to the v2 API in October. You can list, create, view and delete stores and the items in them from Go code.
Improved SDKs
Sorting in the TypeScript content client
Version 2.0.2 of @quantcdn/quant-client, the TypeScript client for the content API, can sort the list of items in a project, such as pages, files and redirects. Pass sort_field and sort_direction to project.meta(). For example, last_modified and desc list the most recently changed items in the project first.
File uploads and asset detection in the TypeScript content client
In @quantcdn/quant-client versions before 2.0.3 (the TypeScript client for the content API), project.file() could not upload files. Version 2.0.3 fixes uploads and renames the file payload field location to url. Before version 2.0.4, project.markup() still asked the API to detect linked assets, such as images and stylesheets, when you set findAttachments: false. It now follows the value you set.
Rename the location field to url in your project.file() calls when you upgrade to version 2.0.3 or later.