IBM Cloud App Configuration
Feature flags and runtime properties per environment, evaluated by SDKs against targeting rules.
- Provider
- ibm
- Category
- Operations
- Official docs
- https://cloud.ibm.com/docs/app-configuration
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| killSwitches | boolean | — | no | true | ▸ true |
| managed | boolean | — | no | false | ▸ true |
| propertyStore | boolean | — | no | true | inherited |
| stagedRollout | boolean | — | no | false | inherited |
| targetingSegments | boolean | — | no | false | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
No rule reads this kind yet. That is a gap, not a guarantee.
nodes:
- { id: "app-configuration", component: "ibm-app-configuration" }AWS AppConfigaws-appconfigAzure App Configurationazure-app-configurationCloudflare Flagshipcloudflare-flagshipApollo Configapollo-configConfigCatconfigcatGeneric feature flag servicefeature-flag-serviceFlagsmithflagsmithFliptfliptGrowthBookgrowthbookLaunchDarklylaunchdarklyOptimizely Feature ExperimentationoptimizelyHarness FMEsplitSpring Cloud Config Serverspring-cloud-configStatsigstatsigUnleashunleashFirebase Remote Configgoogle-firebase-remote-configConfigMapk8s-config-map
# yaml-language-server: $schema=../../schema/component.schema.json # IBM Cloud App Configuration: feature flags and runtime properties held per environment and # collection, evaluated against targeting rules and percentage rollouts by the SDKs in the # application ("App Configuration"). A flag can be toggled off for everyone, so kill switches are # the basic use; segment rollouts are configured per flag. schemaVersion: "1" type: "component" id: "ibm-app-configuration" kind: "feature-flag-service" provider: "ibm" docs: "https://cloud.ibm.com/docs/app-configuration" defaults: managed: true killSwitches: true properties: targetingSegments: type: "boolean" default: false propertyStore: type: "boolean" default: true