Release 12.0 - 231003.12.0
about 1 year ago by Tayler Kemsley
This update allows users greater flexibility in managing their Stellate edge cache.
New Features
1. Enhanced Cache Rule Management
Previously, a fixed 60-second cache was applied to all queries. With this release:
- The default 60-second cache remains but is now customizable.
- Use the
setCacheConfig
mutation to set specific caching rules.
Example:
mutation {
setCacheConfig(
rules: [
{ types: ["Query"], max_age: 3600 }
{ types: ["Query.getSkylarkSet", "Query.listSkylarkSet"], max_age: 86400 }
{ types: ["Query.getAsset"], max_age: 0 }
]
) {
rules {
types
stale_while_revalidate
max_age
}
}
}
This means:
- By default, all
Query
requests have a 1-hour cache. getSkylarkSet
andlistSkylarkSet
queries are set to cache for 24 hours.- The
getAsset
query is set to have no caching.
Remember: This query replaces any existing rules with the ones provided.
To view current rules, use the getCacheConfig
query:
query {
getCacheConfig {
rules {
types
stale_while_revalidate
max_age
}
}
}
2. Cache Purging
Now, you can clear the Skylark edge cache using the new purge query. Options include:
- Clear the entire cache
- Clear cache of a specific
type
- Clear cache of a specific
object
Example to clear all:
mutation {
purgeCache(all: true) {
all
}
}
Bug Fixes
- Resolved a glitch where background tasks appeared as "failed" when linking availability rules, despite successful completion.