Configuration as Code with IBM Cloud App Configuration

Why Configuration as Code?

Configuration as Code bring many benefits.

IBM Cloud App Configuration and Configuration as Code

Feature flags when centrally managed by App Configuration provides the benefit of decoupling the deployment of code from a release. Specifically this comes in handy when the features to be released with minimal risk. Features can be toggled off when a major bug slips in. This gives the flexibility of maintaining the configuration as any other source code while getting the benefit of IBM Cloud App Configuration. IBM Cloud App Configuration can be used as a centralized configuration and also update the configuration without redeploying the entire application.

Sync config file changes to IBM Cloud App Configuration

When the configuration file is maintained in git, git actions can be used to sync the approved configuration back to the App Configuration instance. This is an automated process integrated into git, which can trigger the updates of configuration changes made to the git file to IBM Cloud App Configuration service.

Summary

IBM Cloud App Configuration provides the flexibility of maintaining the configuration as code and a centralized feature flag system. This helps in reducing the risk of feature releases along with the governance required in maintaining the configurations.

Resources

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store