image_ref field.
Images are typically produced by the bake process. When you bake a recipe, the platform executes it against a base image and writes the resulting image back to the catalog with provenance metadata. Baked images are immutable: you cannot update them. Deleting a baked image with murmur rm image <name> also deletes its cloud artifact (the GCE image or the AMIs). Deleting a hand-authored image removes only the catalog record. You can also author images manually to reference existing AMIs or GCE images that you manage outside Murmur.
Fields
A new baked image inherits its recipe’sworkspace_use policy. Reusing an existing baked image preserves its stored policy. Baked records are immutable to tenant callers, including their admission policy.
Exactly one of
aws or gce must be set.
AWS source fields
Setaws to reference one or more AMIs:
GCE source fields
Setgce to reference a GCE disk image or image family:
Provenance fields
Provenance is present on baked images and records what produced them. It is set automatically by the bake process and cannot be set viamurmur set.
Examples
Hand-authored GCE image
Hand-authored AWS image
Baked image (generated by the platform)
Baked images appear in the catalog after a successful bake. Their names are generated and they carry provenance metadata:Listing images
Reading a single image
Errors
Related
- Images: concept overview
- Recipes: the provisioning template that produces baked images
- Workspaces: the resource that references an image via
image_ref murmur set: CLI command for creating and updating catalog resourcesmurmur get: CLI command for reading catalog resourcesmurmur bake: bakes images from recipes