Local dev configuration (airplane.dev.yaml)
The context in which tasks and views are executed locally can be customized through local
resources, config variables, and environment variables.
This configuration is managed via the Studio UI and persisted to an
airplane.dev.yaml
file.The following is a complete reference of fields supported by the
airplane.dev.yaml
file.For more information, see Studio.
Resources
Resources
Resources are registered with the local dev server when developing a task
locally.
resources
list
Top-level field that stores a list of resources.
yamlCopied1// airplane.dev.yaml2resources:3- slug: db4name: My database5kind: postgres6# The following fields are resource-specific.7host: localhost8port: "5432"9ssl: disable10username: postgres11password: password12database: postgres
Common fields
Common fields
A unique identifier that is used to reference the resource in a task. This should match the slug
that's included in your resource
attachments.
A human-readable name for the resource.
The kind of the resource—for a complete list of resource kinds, see the Resource
page.
Resource-specific fields
Resource-specific fields
For an exhaustive list of fields that a resource of a specific kind can support, see the
Resources reference page.
Config variables
Config variables
Config variables are referenced by environment variables and config attachments and are loaded into
the runtime when developing a task locally.
configVars
object
Top-level field that stores a map of config variables.
yamlCopied1// airplane.dev.yaml2configVars:3API_KEY: 12344<key>: <value>
The name of the config variable.
The value of the config variable.
Environment variables
Environment variables
Environment variables are loaded into the runtime when developing a task locally.
envVars
object
Top-level field that stores a map of environment variables.
yamlCopied1// airplane.dev.yaml2envVars:3MY_ENV_VAR: foo4<key>: <value>
The name of the environment variable.
The value of the environment variable.