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, you choose a mount path. The config file appears as:

<mount-path>/config.yaml    # The YAML content

Your application reads it from this path. For example, a service might reference /etc/config/app/config.yaml.

Rotation

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

• File-mounted containers pick up the new config automatically within about 60 seconds. No manual action needed.
• If you need to force a restart, use the Redeploy button on the Consumers panel.

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)