Feature Toggle Promotion via CI/CD Pipeline
summary
Concrete recipe for promoting feature flags through CI/CD using Feature Hub, an ft.yaml declared in the decider component, and automated sync/validation steps. Pipelines validate ft.yaml, check for duplicate IDs, create artifacts, push toggles into SIT, take a JSON snapshot, lock toggles during regression, verify no version changes, then promote the exact snapshot through replica and prod via API. Demo shows live toggling via Feature Hub SDKs and performance tests (200 users → ~129 RPS, 300 → ~1600 RPS).
AI-written summary · about
chapters (6)
- 0:00Introduction to feature toggles
- 2:51Decoupling with feature toggles
- 12:11First demo: enabling features
- 15:54Feature Hub architecture
- 21:23Automating toggle promotion
- 35:54Final demo: automated deployment
related talks
01h 09mFeature flags: the toggle, the A/B test and the canary
51mFeature Toggles, or How to Deploy Features Without a Release
20mFeature Flag-Driven Development… in Reverse
31mFlag-tastic and Fearless: Feature Flags Meet K8s for Deployments That Sing!
40mContinuous Delivery for Python with Feature Flags
08mThe Art of Feature Flagging
41mFeature Flags: Separate Deployment from Feature Release
38mTesting in Production