vtex-io-service-configuration-apps

Share configuration across VTEX IO service apps by defining a versioned configuration schema and injecting settings via a dedicated configuration app. Consumers opt in through manifest.json using settingsType or GraphQL @settings, decoupling runtime configuration from service code.

Decouple runtime settings from VTEX IO service code by establishing a shared configuration contract. Define a stable schema in configuration/schema.json, expose it through a configuration app, and inject values into services rather than hard-coding them.

Set up a configuration schema by creating a configuration app with a configuration/schema.json file that defines the contract. Add a matching configuration.json in the configuration/ folder and wire the service manifest to receive injected settings.

Yes, injecting VTEX IO settings requires a service app declaring the configuration builder in its manifest.json. The service then explicitly opts in to the shared contract using settingsType or GraphQL @settings entries.

Shared configuration contracts enable cross-service sharing, versioning, and independent lifecycle management of configuration separate from the consuming service. This prevents configuration drift and removes the need to deploy service code changes for setting updates.

Yes, VTEX IO service configuration supports independent lifecycle and versioning. By centralizing settings in a dedicated configuration app with a defined schema, you can update and version configuration without redeploying the consuming service code.