Publish and rollback

Goal

Publish configuration deliberately and roll back when a change misbehaves.

Prerequisites

• config.read / config.write.

Publish

1. Open Ops → Config.
2. Review pending intent (or rely on auto-publish from CRUD).
3. Publish with an optional comment.
4. Proxies receive ConfigChangedMessage (Redis) and pull the snapshot.

Rollback

1. Open Versions.
2. Select a known-good version.
3. Rollback creates a new version copying that payload (history stays immutable) and republishes.

Verify

• Active version number updates in the UI.
• Proxy /ready shows the new configVersion.
• Smoke-test critical routes after every production publish.

Tips

• Prefer small, reviewable publishes.
• Keep Detect-mode WAF changes separate from topology changes when possible.