config-feature-flags

Feature toggles can be managed by applying config keys in default.yaml, per-environment profile overlays, and environment variables to control behavior across different environments. This approach replaces a dedicated feature-flag service.

To add a new feature toggle, store the key in config/default.yaml or apply it via environment variables for ad-hoc runs, then test the toggle across your per-environment profile overlays. This ensures safe, predictable feature gating.

Auditing existing feature flags involves scanning config/default.yaml, profile overlays, and environment reads to identify active toggles. This process also helps identify code-level toggles that are ready for migration to the profile system.

Migrating ad-hoc booleans to the profile system uses a behavior-preserving process with documentation to ensure safe transitions. It moves isolated environment variables into structured profile overlays for better lifecycle management.

Yes, you can control feature toggles per-invocation by passing environment variables for ad-hoc runs. This allows temporary feature gating without modifying the default config or profile overlays.

No, you do not need a dedicated feature-flag service because toggles can be managed at rest through config keys and profile overlays. This provides lifecycle management and auditing without external service dependencies.