murmur patch

Performs a partial update on a catalog resource. Only the specified fields are changed — all other fields are preserved.

Synopsis

murmur patch <kind> <name> --set field=value [--manager NAME] [--force-ownership] [--file-field field.path=filename ...]

Arguments

Name	Type	Required	Description
`kind`	string	yes	The catalog resource kind. Run `murmur describe` to list available kinds.
`name`	string	yes	The resource name to update.
`--set`	string	yes (unless `--file-field` is provided)	Set a field to a value. Format: `field=value`. Repeatable. Accepts dotted paths for nested fields (see Nested fields).
`--file-field`	string	no	Inject file content at a dotted field path. Format: `field.path=filename`. Repeatable.
`--manager`	string	no	Declare the system responsible for this resource (for example, your automation’s name). It is recorded as the resource’s `managed_by` marker. Later writes that do not declare the same manager are refused unless forced. Leave unset for a manual edit.
`--force-ownership`	boolean	no	Patch even when another system manages the resource. Without `--manager`, the patch releases the resource (its `managed_by` marker is cleared). With `--manager`, that manager becomes the new one.

At least one --set or --file-field is required. The resource must already exist: a patch never creates one. A patch is a manual edit and declares no manager, so it is refused when the resource is managed by another system (Terraform, or your own automation). --force-ownership patches anyway, but it does not remove the resource from whatever manages it: if the resource is still in Terraform configuration, the next terraform apply reverts the value and reclaims the marker. murmur get prints the managed_by marker. On markdown kinds (agent-persona, flight, knowledge), patch structured fields. The rendered content field cannot be patched; replace the resource with murmur set instead.

Value type inference

The --set flag infers the value type automatically:

Input	Inferred type	Example
Integer string	integer	`--set max_vms=100`
`true` / `false`	boolean	`--set port_proxy_disabled=true`
Anything else	string	`--set machine_type_ref=murmur-n2-standard-16`

Floating-point values are sent as strings.

Nested fields

A dotted path such as gcp.project builds a nested object, but the update replaces the whole top-level field. --set gcp.project=my-project replaces the placement’s entire gcp block with one that contains only project. To change one nested value, read the resource with murmur get, edit it, and write it back with murmur set.

Examples

Change a pool’s VM limit

murmur patch pool-config default --set max_vms=100

Patched pool-config "default"

Change an environment’s machine type

murmur patch environment staging --set machine_type_ref=murmur-n2-standard-16

Patched environment "staging"

Update multiple fields at once

murmur patch environment staging --set machine_type_ref=murmur-n2-standard-16 --set disk_size_gb=200

Patched environment "staging"

Inject file content into a field

murmur patch recipe python-toolchain --file-field provisioning_script=provision.sh

Patched recipe "python-toolchain"

Errors

Code	Meaning	What to do
`NOT_FOUND`	No resource with that kind and name exists.	Check the name. Run `murmur get` `<kind>` to list available resources.
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur login`, or check your `murmur.local.yaml` configuration.
`INVALID_ARGUMENT`	The kind is not recognized, a field name or value is invalid, or the name is reserved for builtins (`murmur-` prefix).	Run `murmur describe` to check the kind’s schema. Builtins cannot be modified; create your own resource with a different name.
`FAILED_PRECONDITION`	`<kind> "<name>" is managed by "<manager>", which may overwrite this change on its next run; re-run with --force-ownership to write anyway and ...`	Change the resource through the system that manages it, or re-run with `--force-ownership`.
`PERMISSION_DENIED`	Your role does not grant write access to this kind.	Ask a tenant admin for access.

Catalog — concept overview
murmur get — read a resource or list resources of a kind
murmur set — create or fully replace a resource
murmur rm — delete a resource
murmur describe — show schema information for a kind

Getting Started

Core Concepts

Guides

Synopsis

Arguments

Value type inference

Nested fields

Examples

Change a pool’s VM limit

Change an environment’s machine type

Update multiple fields at once

Inject file content into a field

Errors

​Synopsis

​Arguments

​Value type inference

​Nested fields

​Examples

​Change a pool’s VM limit

​Change an environment’s machine type

​Update multiple fields at once

​Inject file content into a field

​Errors

​Related

Synopsis

Arguments

Value type inference

Nested fields

Examples

Change a pool’s VM limit

Change an environment’s machine type

Update multiple fields at once

Inject file content into a field

Errors

Related