Skip to main content
PATCH
/
v2
/
deployments
/
{id}
Update deployment
curl --request PATCH \
  --url https://api.sfcompute.com/v2/deployments/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "my-resource-name",
  "node_template": "ntmpl_k3R-nX9vLm7Qp2Yw5Jd8F",
  "target_node_count": 123,
  "node_name_template": "my-fleet-{{nanoid(9)}}"
}
'
{
  "id": "<string>",
  "resource_path": "<string>",
  "owner": "<string>",
  "workspace": "<string>",
  "name": "<string>",
  "object": "deployment",
  "capacity": "cap_k3R-nX9vLm7Qp2Yw5Jd8F",
  "node_template": "ntmpl_k3R-nX9vLm7Qp2Yw5Jd8F",
  "target_node_count": 123,
  "node_name_template": "<string>",
  "status": {
    "state": "info",
    "message": "<string>"
  },
  "created_at": 1738972800,
  "updated_at": 1738972800
}

Authorizations

​
Authorization
string
header
required

Create an API token using sf tokens create or at https://sfcompute.com/account/api-keys.

Path Parameters

​
id
string
required

A resource path like 'sfc:deployment:acme:prod:my-deployment' or an ID. Resource paths are human-readable but not stable - they change when resources are renamed or moved. IDs are stable and permanent.

Pattern: (depl_[0-9a-zA-Z_-]{1,21})|(sfc:deployment:[a-zA-Z0-9._-]+(:[a-zA-Z0-9._-]+){1,3})
Example:

"depl_k3R-nX9vLm7Qp2Yw5Jd8F"

Body

application/json
​
name
null | string
Required string length: 1 - 255
Pattern: [a-zA-Z0-9][a-zA-Z0-9._-]{0,254}
Example:

"my-resource-name"

​
node_template
null | string

A resource path like 'sfc:node_template:acme:prod:my-node_template' or an ID. Resource paths are human-readable but not stable - they change when resources are renamed or moved. IDs are stable and permanent.

Pattern: (ntmpl_[0-9a-zA-Z_-]{1,21})|(sfc:node_template:[a-zA-Z0-9._-]+(:[a-zA-Z0-9._-]+){1,3})
Example:

"ntmpl_k3R-nX9vLm7Qp2Yw5Jd8F"

​
target_node_count
integer<int32> | null
​
node_name_template
null | string

A name template using {{variable}} syntax. Available variables: {{adjective}} (~128 random adjectives), {{noun}} (~128 random nouns), {{nanoid(N)}} (N-character alphanumeric identifier, 1 ≤ N ≤ 21). The template must produce enough unique combinations to avoid collisions — equivalent to at least the default template {{adjective}}-{{noun}}-{{nanoid(6)}} (~1 quadrillion possibilities). Must start with an alphanumeric character. Resolved names are limited to 255 characters.

Maximum string length: 512
Example:

"my-fleet-{{nanoid(9)}}"

Response

Deployment updated.

​
id
string
required
Pattern: depl_[0-9a-zA-Z_-]{1,21}
Example:

"depl_k3R-nX9vLm7Qp2Yw5Jd8F"

​
resource_path
string
required

A resource path for a deployment resource. Format: sfc:deployment:::.

Pattern: sfc:deployment:([a-zA-Z0-9._-]+:){2}[a-zA-Z0-9._-]+
Example:

"sfc:deployment:<account_id>:<workspace>:<name>"

​
owner
string
required
Required string length: 1 - 255
Pattern: [a-zA-Z0-9][a-zA-Z0-9._-]{0,254}
Example:

"my-resource-name"

​
workspace
string
required
Required string length: 1 - 255
Pattern: [a-zA-Z0-9][a-zA-Z0-9._-]{0,254}
Example:

"my-resource-name"

​
name
string
required
Required string length: 1 - 255
Pattern: [a-zA-Z0-9][a-zA-Z0-9._-]{0,254}
Example:

"my-resource-name"

​
object
string
default:deployment
required
read-only
Allowed value: "deployment"
​
capacity
required

ID (default) or expanded summary when using expand parameter

Pattern: cap_[0-9a-zA-Z_-]{1,21}
Example:

"cap_k3R-nX9vLm7Qp2Yw5Jd8F"

​
node_template
required

ID (default) or expanded summary when using expand parameter

Pattern: ntmpl_[0-9a-zA-Z_-]{1,21}
Example:

"ntmpl_k3R-nX9vLm7Qp2Yw5Jd8F"

​
target_node_count
integer<int32>
required
​
node_name_template
string
required

A name template using {{variable}} syntax. Available variables: {{adjective}} (~128 random adjectives), {{noun}} (~128 random nouns), {{nanoid(N)}} (N-character alphanumeric identifier, 1 ≤ N ≤ 21). The template must produce enough unique combinations to avoid collisions — equivalent to at least the default template {{adjective}}-{{noun}}-{{nanoid(6)}} (~1 quadrillion possibilities). Must start with an alphanumeric character. Resolved names are limited to 255 characters.

Maximum string length: 512
Example:

"my-fleet-{{nanoid(9)}}"

​
status
object
required
​
created_at
integer<int64>
required

Unix timestamp.

Example:

1738972800

​
updated_at
integer<int64>
required

Unix timestamp.

Example:

1738972800