A couple solutions I've seen before - Config gets generated to a deploy and saved as <version>.json. Code downloads config file matching its own version or fai

A couple solutions I've seen before - Config gets generated to a deploy and saved as <version>.json. Code downloads config file matching its own version or fails to start (this is a nice one since rollbacks becomes vary deterministic and code rollback is the same process as config rollback) - Deploy code first and verify it's updated and working correctly before changing feature flag config (this one is still prone to errors without automation) The first one can be done on Kubernetes using kustomize ConfigMap generator. The system I worked on used object storage for the config file and deploy tooling to generate it from a key value store at deploy time