JSON Configs

A JSON config stores a JSON configuration file in the Bahriya platform. The content is validated on upload, versioned, and delivered to your containers as a mounted file.

When to use a JSON config

• Your application reads configuration from a JSON file at startup (for example config.json or appsettings.json)
• You want to change configuration without rebuilding your container image
• You need the same configuration file available across multiple containers or regions
• You want to version configuration changes and roll back if needed

What Bahriya stores

When you upload a JSON config, Bahriya validates that the content is syntactically correct JSON and stores it alongside metadata:

Unlike vault items, JSON config content is shown back in the console, API responses, and CLI output.

Mounting in containers

When you attach a JSON config to a container, the mount path you choose is the exact file the content is delivered as -- not a directory. Enter the full file path your application expects:

/etc/config/app/config.json    # the mount path IS the file

The file is placed at exactly that path and sits alongside the other files already in that directory -- it does not replace or hide them.

Rotation

Rotation creates a new version of the config. The previous version is retained for rollback. After rotation:

• Because the config is mounted as a single exact file, the running container does not pick up the new version automatically. Use the Redeploy button on the Consumers panel to roll the container onto the rotated version.

Pricing

JSON configs are billed at $0.01 per month while they exist, plus $0.05 per region per month when attached to a project.

See also

• Deploy JSON Configs with Terraform
• Deploy JSON Configs with Reis (YAML Mode)
• Deploy JSON Configs with Reis (Flag Mode)