Configuration#
Two files and the environment decide what a deployment does, and these pages
are split by the one you have open. profile.yml is the file you edit: the
build profile a facility writes, and the input osprey build renders from.
config.yml is what a running project reads – rendered from the profile, so
it is where you look a setting up; a change that should survive the next build
belongs in the profile. Anything that must not sit in a committed file, such as
API keys and per-host values, arrives from the environment instead. Scenario
files, the fourth page, belong to the simulator.
Every key a build profile accepts, from the core field table through
config: overrides, MCP servers, tool permissions, services and
dependencies – and what the build does with each.
The rendered runtime file: the health: diagnostic suite, the web:
block behind the browser UI, and the deployment keys that choose each
service’s container image.
The environment variables the OSPREY CLI reads and where each belongs –
provider keys live in the deployment repository’s .env.
Every key a simulator scenario file accepts, the archive event shapes, and what each channel fault does.