3.7 Config Server (/config-server, /config-server/query)
Purpose: a tracking system for configuration-value changes that is independent of release tickets (but can optionally be linked to one). The backend only requires login, with no role restriction — any signed-in user can add / edit / delete.
Submit form fields
| Field | Required | Notes |
|---|---|---|
| Environment | TP / TC / GCP / TC+TP / TC+TP+GCP | |
| Project Name | ✓ | — |
| Tag Name | ✓ | — |
| Category | Redis / Project / Limit / Switch / Key permission / API Key management / other (when "other" is chosen, "Category (custom)" becomes required) | |
| Key | ✓ | — |
| New value (Value) | at most 2500 characters | |
| Deploy | yes / no, default yes | |
| Ticket number | search and link an existing release ticket | |
| Description | ✓ | — |
Query page
Filters: environment / category / ticket number → Query. The table has an "Updated" column (badge: yes = applied, no = pending); every field can be edited in place (the updated flag itself is read-only on this screen — the actual apply is done through momo-cogwork calling with a config-server:write API key; see §2.4 for the flow).