Configuration rollout, rollback, and long polling

A configuration center must control how changes become visible. Editing a value, publishing a version, selecting a rollout scope, and delivering an update to listeners are separate operations.

Confirmed facts

• Max config content length: 20,000 characters.
• Max page size: 100.
• Publish, progressive delivery, and rollback are supported.
• One file can keep multiple active gray releases; full publish does not end them; stop-gray is per release.
• When a client matches several grays, the newest by version/mtime wins.
• Clients watch via SSE or long polling.
• Pole Agent confirmed writes become drafts only; humans still publish.

Recommended rhythm

1. Create the group and file in the correct Namespace.
2. Edit the draft and validate content.
3. Publish one or more grays by client labels; watch hits under Release history → Gray and Subscriptions.
4. “Submit as formal draft” on the validated gray, then full-publish; keep or stop other grays independently.
5. On issues, roll back full or stop the relevant gray; audit History.

Open measurements

This site does not publish listener latency or concurrency claims without reproducible benchmarks.

Related docs

• Configuration guide (multi-gray)
• Progressive delivery practice
• Using the Console