maton function update

maton function update <function-id> [flags]

Update a function. Only the flags you pass are changed.

For publishing code by hand, prefer maton function deploy: it takes no function ID, having recorded one when it first created the function. Reach for this command in scripts, where an explicit ID and a single PATCH are the point, and for the two things deploy will not do — renaming, and rolling back.

Pass --dir or --file to publish new code, which creates a new version. Roll back by pointing the function at an existing version with --version <n>; there is no separate activate or deploy step, so --version cannot be combined with new code.

A function’s runtime is immutable, so there is no --runtime flag. Unlike create, the handler is sent only when --handler is passed explicitly: otherwise the server keeps the handler the current version already records.

--handler on its own publishes a new version. It is not a metadata edit like --name: the handler belongs to a version, so changing it re-reads the current version’s files and publishes them again under the new handler. Nothing is uploaded, and the code is unchanged, but the version number moves.

Renaming a function reallocates its URL. The old label is released immediately, so the previous URL stops resolving for everyone holding it — including any webhook configured elsewhere.

Options

--description <string>

New description

-D, --dir <string>

Directory to upload as a new version

--dry-run

Print the bundle manifest and exit without uploading

--file <local[:remote]>

File to upload as local[:remote] (repeatable)

--handler <<module>.<symbol>>

Handler as <module>.<symbol>, which publishes a new version (unchanged when omitted)

--ignore <stringArray>

Glob to exclude from --dir (repeatable)

-q, --jq <expression>

Filter JSON output using a jq expression

--json <fields>

Output JSON with the specified fields

--name <string>

New name, which reallocates the URL

--network-policy <string>

Whether the sandbox may reach the network: {ALLOW_ALL|DENY_ALL}

--no-default-ignore

Do not apply the default ignore list

-t, --template <string>

Format JSON output using a Go template; see "maton help formatting"

--version <int> (default 0)

Existing version to roll back to

--visibility <string>

Who can see the function: {PRIVATE|PUBLIC|UNLISTED}

Options inherited from parent commands

-p, --profile <string>

Profile to use for this invocation (overrides the active profile; also reads MATON_PROFILE)

JSON Fields

account_id, created_at, description, function_id, name, network_policy, runtime, star_count, updated_at, url, version, view_count, visibility

Examples

# Publish new code
$ maton function update 9f3c1e2a-0b7d-4c11-9d2e-5f6a7b8c9d01 --dir ./my-fn

# Roll back to version 1
$ maton function update 9f3c1e2a-0b7d-4c11-9d2e-5f6a7b8c9d01 --version 1

# Point at a different symbol, publishing a new version of the same files
$ maton function update 9f3c1e2a-0b7d-4c11-9d2e-5f6a7b8c9d01 --handler main.webhook

# Make it public
$ maton function update 9f3c1e2a-0b7d-4c11-9d2e-5f6a7b8c9d01 --visibility PUBLIC

See also

• maton function