Skip to main content

Feature flags

A feature flag turns part of CMDX on or off without a new deploy. This page lists the flags the backend enforces today. Each flag is a boolean config key, so it follows the scope rules on the configuration page.

note

Which other flags CMDX enforces is still being decided. Until then, this page lists only the flags the backend enforces today. Code reads a flag with resolve_setting from core.config.resolve.

Summary​

KeyTypeDefaultScopesTurns on or off
calendar.calendar_enabledbooleantrueglobal, tenantThe calendar

Details​

calendar.calendar_enabled​

Turns the calendar on or off for the whole installation or for one tenant.

  • Resolution: the first match wins, in this order: the tenant's stored entry, the global stored entry, the CALENDAR_ENABLED environment variable, then the default. The default is on. At each scope, an entry stored under the older key calendar_enabled also counts.
  • Values: true, 1, yes and on mean on, in any case. Any other stored value means off. In CALENDAR_ENABLED, false, 0, no and off mean off, and any other value is ignored.
  • When off: calendar requests return HTTP 403 with the error code CALENDAR_PERMISSION_DENIED. Revoking a calendar feed token with DELETE /api/v1/calendar/feed/token/<token-id> still works when the flag is off.
  • Exception: platform super administrators can use the calendar even when the flag is off.