Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Name of the Blueprint.
(Optional) Use a RepositoryInspection a source of a Blueprint build. The Dockerfile will be automatically created based on the RepositoryInspection contents.
A list of commands to run to set up your system.
Parameters to configure your Devbox at launch time.
(Optional) Map of paths and file contents to write before setup.
(Optional) User defined metadata for the Blueprint.
(Optional) Map of mount IDs/environment variable names to secret names. Secrets can be used as environment variables in system_setup_commands. Example: {"GITHUB_TOKEN": "gh_secret"} makes 'gh_secret' available as GITHUB_TOKEN.
Response
OK
Blueprints are ways to create customized starting points for Devboxes. They allow you to define custom starting points for Devboxes such that environment set up can be cached to improve Devbox boot times.
The id of the Blueprint.
The name of the Blueprint.
The status of the Blueprint build.
provisioning, building, failed, build_complete The state of the Blueprint.
created, deleted Creation time of the Blueprint (Unix timestamp milliseconds).
The parameters used to create Blueprint.
Build completion time of the Blueprint (Unix timestamp milliseconds).
The failure reason if the Blueprint build failed, if any.
out_of_memory, out_of_disk, build_failed The ID of the base Blueprint.
List of ContainerizedServices available in the Blueprint. Services can be explicitly started when creating a Devbox.
Whether this Blueprint is publicly accessible to all users.
User defined metadata associated with the blueprint.
Capabilities that will be available on Devbox.
