Change-event sources
Flag services and CI tools post changes to Watchtower; they appear as chart annotations and as candidates in change analysis (/analysis/changes).
Set up
Settings, Change sources, pick the provider, Create (needs
manage_connectors), orPOST /v1/projects/{p}/change-sources {"kind": "...", "mapping": {"service": "api", "env": "production"}}.The response holds the URL
/v1/changes/{source_id}and asecret, shown once. Only its SHA-256 is stored.mapping.service/mapping.envare defaults for events that carry neither.Configure the provider to POST to that URL.
Verification per provider
Provider | How the request is checked |
|---|---|
LaunchDarkly |
|
Statsig |
|
CircleCI |
|
Unleash | the secret as |
Flagsmith | the secret in |
EventBridge | the secret as the API-destination key ( |
Buildkite | the secret as |
Harness | the secret in |
signing_key is returned at create for the HMAC providers: the hex of the SHA-256 of the secret, the same value the server keeps. Treat it as a secret too. A failed check is 401 and stores nothing.
Events
Each payload becomes change_events rows (kind flag, deploy or pipeline) with service, env, actor, summary, url and at in the event; fields that are not mapped stay in details. Redelivery of the same provider event id is ignored (the response says how many were stored). Limits: 600 requests per minute per source (429 with Retry-After), body up to 256 KiB (413). Delivery is at-least-once; a provider that retries is safe.