Skip to main content

Feature flag / general config management dashboard — idea discussion

Context​

Giovanni Massimiliano (Jovi) proposed building a dashboard to manage CDP's feature flags and general config, so they're easy to view and manage. Maulana Ghozi Humama raised it with Puji Triwibowo to decide whether to build this into an existing Qontak client surface or as a standalone web app. Access should be limited to the CDP squad only. The underlying API is already ready, using basic auth.

Notes​

  • Example feature flag case raised: custom_field_limitation — toggling it between general scope and per-CID scope.
  • Puji Triwibowo suggested consolidating this into clients.qontak.net rather than a separate app, with an added whitelist of who can update, plus audit logs — similar to the access model used in qontak-one-migration (only whitelisted people can access).
  • Giovanni Massimiliano (Jovi) asked to confirm the whitelist would still be hardcoded.
  • Giovanni Massimiliano (Jovi) noted that for a more scalable internal platform, a proper user-role model (minimum: engineer / non-engineer role per module) would be needed, but flagged that as a fairly sizable effort.
  • Puji Triwibowo noted qontak-one-migration uses SQLite for its whitelist, with a superadmin able to add entries; proposed starting with that same approach.
  • Puji Triwibowo: if TS (Technical Support) later needs direct update access — e.g. a whitelisted person enabling/disabling a specific feature for a certain CID — that can be improved later. For now, TS/CS needs on clients.qontak.net are read-only.

Decisions / changes​

  • Direction leaning toward consolidating the feature-flag/config management UI into clients.qontak.net (not a standalone web app), gated by a whitelist (SQLite-backed, superadmin can add entries — following the qontak-one-migration pattern) plus audit logs. Unconfirmed as a final decision — discussion was still in progress.
  • Scope for now: CDP squad-only management access; TS/CS access on clients.qontak.net stays read-only.
  • Full user-role model (engineer / non-engineer) deferred as a future improvement given its effort.

Follow-ups​

  • TBD — formalize this into a PRD/RFC once the approach (consolidate into clients.qontak.net vs. standalone app) and whitelist mechanism are confirmed.