YAML Configs

A YAML config stores a YAML configuration file in the Bahriya platform. The content is validated for correct YAML syntax, encrypted at rest, and delivered to your containers as a mounted file.

When to use a YAML config

• Your application reads its configuration from a YAML file at startup
• You need to share a structured configuration across multiple containers or regions
• You want to version and rotate configuration without redeploying your application
• Your application expects a .yaml or .yml config file at a specific path

What Bahriya stores

When you upload a YAML config, Bahriya validates the syntax and stores the content:

The content is shown back in the console, API responses, and CLI output when you view the detail of a YAML config.

Mounting in containers

When you attach a YAML 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.yaml    # 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

YAML 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 YAML Configs with Terraform
• Deploy YAML Configs with Reis (YAML Mode)
• Deploy YAML Configs with Reis (Flag Mode)