Purge-Cache Exchanges


The purge-cache service, typically available at purge-cache.taskcluster.net, is responsible for publishing a pulse message for workers, so they can purge cache upon request.

This document describes the exchange offered for workers by the cache-purge service.

Exchanges

NameExchangeSummary
purgeCacheexchange/taskcluster-purge-cache/v1/purge-cachePurge Cache Messages

purgeCache

Exchange
exchange/taskcluster-purge-cache/v1/purge-cache
Signature
"purgeCache(routingKeyPattern)"

When a cache purge is requested a message will be posted on this exchange with designated provisionerId and workerType in the routing-key and the name of the cacheFolder as payload

Routing Key

IndexNameSummary
0
routingKeyKind

Identifier for the routing-key kind. This is always 'primary' for the formalized routing key.

constant-key

1
provisionerId

provisionerId under which to purge cache.

2
workerType

workerType for which to purge cache.

Message Payload

Purge Cache Message (source)

Message reporting that a specific cache should be purged

versioninteger
  • 1

Message version

provisionerIdstring[1:22]^([a-zA-Z0-9-_]*)$

provisionerId under which the workerType we want to purge for exists.

workerTypestring[1:22]^([a-zA-Z0-9-_]*)$

workerType we wish to purge cache for.

cacheNamestring

Name of cache to purge. Notice that if a workerType have multiple kinds of caches (with independent names), it should purge all caches identified by cacheName regardless of cache type.