---
next_cursor: eyJzY29yZSI6MCwic2VxIjoxNjg0LCJzaW5jZSI6bnVsbCwidG9vbCI6ImRvY3RsIiwidiI6MX0
has_more: true
next: https://sincecutoff.com/v1/changes.md?tool=doctl&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxNjg0LCJzaW5jZSI6bnVsbCwidG9vbCI6ImRvY3RsIiwidiI6MX0
items: 10
---
# sincecutoff.com changes: doctl

## doctl apps adds cancel-job-invocation (doctl, 2026-01-22)
Published 2026-10-19
- slug: doctl-apps-adds-cancel-job-invocation-72a21719746d
- score: 0.93

How to use it:

When you need to cancel a specific App Platform job invocation, run `doctl apps cancel-job-invocation` with the app ID and job invocation ID.

Examples:

```
doctl apps cancel-job-invocation <app id> <job invocation id>
```

- why_it_matters: Cancel a job invocation for a DigitalOcean app.
- sources: <https://github.com/digitalocean/doctl/releases/tag/v1.149.0>, <https://github.com/digitalocean/doctl/pull/1792>, <https://github.com/digitalocean/doctl/blob/v1.149.0/commands/apps.go>, <https://docs.digitalocean.com/reference/doctl/reference/apps/cancel-job-invocation/>, <https://docs.digitalocean.com/reference/doctl/reference/auth/init/>
- gotchas: "Version: v1.149.0"; "<app id> (required): ID of the app."; "<job invocation id> (required): ID of the job invocation to cancel."; "Prerequisite: Authenticate doctl with a DigitalOcean API token or provide one with the global `--access-token` flag."

## doctl apps adds autoscaling event commands and logs (doctl, 2026-03-18)
Published 2026-10-19
- slug: doctl-apps-adds-autoscaling-event-commands-and-logs-f62e55976c4b
- score: 0.95

How to use it:

For an App Platform app, use `list-events` to inspect events; use `cancel-event` with the app and event IDs to cancel an in-progress autoscaling event. To retrieve event logs, pass the event ID to `apps logs` and set the type to `autoscale_event`.

Examples:

```
doctl apps list-events <app-id>
```

```
doctl apps cancel-event <app-id> <event-id>
```

```
doctl apps logs <app-id> <component-name> --event-id <event-id> --type autoscale_event
```

- why_it_matters: Inspect an App Platform app's autoscaling events, cancel one, or retrieve its event logs.
- sources: <https://github.com/digitalocean/doctl/releases/tag/v1.152.0>, <https://github.com/digitalocean/doctl/pull/1810>, <https://docs.digitalocean.com/reference/doctl/reference/apps/list-events/>, <https://docs.digitalocean.com/reference/doctl/reference/apps/cancel-event/>, <https://docs.digitalocean.com/reference/doctl/reference/apps/logs/>
- gotchas: "Version: v1.152.0"; "<app-id> (required): App ID; required by the list-events and cancel-event command syntax."; "<event-id> (required): Event ID used by cancel-event; with logs, supplied as the value of `--event-id`."; "<component-name>: Component whose logs to retrieve; defaults to all components."; "--event-id: Selects logs for a specific autoscaling event ID."; "--type: Selects the log type; defaults to `run`. `autoscale_event` is a supported type."; "Docs conflict: The current official CLI reference pages are generated from doctl v1.178.0, v1.173.0, and v2.0.0, later than the card’s v1.152.0; exact v1.152.0 command details could not be verified from those pages."

## doctl dedicated-inference endpoints and tokens commands (doctl, 2026-03-31)
Published 2026-10-19
- slug: doctl-dedicated-inference-endpoints-and-tokens-commands-1bdf86bd6417
- score: 0.90

How to use it:

When managing a dedicated inference endpoint from a repository workflow, use the `doctl dedicated-inference` command group. Update it with a JSON or YAML spec using `--spec` (use `-` for stdin), and optionally pass a Hugging Face token for gated models.

Examples:

```
doctl dedicated-inference update <dedicated-inference-id> --spec <spec.json>
```

```
doctl dedicated-inference update <dedicated-inference-id> --spec <spec.yaml> --hugging-face-token "<hugging-face-token>"
```

```
cat <spec.json> | doctl dedicated-inference update <dedicated-inference-id> --spec -
```

- why_it_matters: Create, inspect, list, update, or manage a dedicated inference endpoint from a repository workflow.
- sources: <https://github.com/digitalocean/doctl/releases/tag/v1.154.0>, <https://github.com/digitalocean/doctl/pull/1825>, <https://docs.digitalocean.com/reference/doctl/reference/dedicated-inference/update/>
- gotchas: "Version: v1.154.0"; "<dedicated-inference-id> (required): ID of the endpoint to update."; "--spec (required): Path to a JSON or YAML spec; `-` reads it from stdin."; "--hugging-face-token: Hugging Face token for accessing gated models."; "--format: Comma-separated output columns. Allowed: `ID`, `Name`, `Region`, `Status`, `VPCUUID`, `PublicEndpoint`, `PrivateEndpoint`, `CreatedAt`, `UpdatedAt`."; "Prerequisite: Authenticate `doctl` with a DigitalOcean API V2 access token."; "Update requires a dedicated inference ID argument; the command returns an error when it is missing."; "Docs conflict: Current CLI reference is generated from doctl v1.169.0, later than the card's v1.154.0. It documents the same update interface, but does not establish the v1.154.0 behavior for every operation in the card."

## doctl droplets create adds --public-networking (doctl, 2026-03-31)
Published 2026-10-19
- slug: doctl-droplets-create-adds-public-networking-0e4b16fc665b
- score: 0.92

How to use it:

When creating a Droplet, set public networking explicitly with the documented doctl flag; `false` disables it and `true` enables it.

Examples:

```
doctl compute droplet create <droplet-name> --size <size-slug> --image <image-slug> --enable-public-networking=false
```

- why_it_matters: Create a droplet with a chosen public-networking setting.
- sources: <https://github.com/digitalocean/doctl/releases/tag/v1.154.0>, <https://docs.digitalocean.com/products/droplets/how-to/create-private-droplet/>, <https://docs.digitalocean.com/reference/doctl/reference/compute/droplet/create/>, <https://docs.digitalocean.com/reference/api/scopes/droplet/create/>
- gotchas: "Version: v1.154.0"; "--enable-public-networking: Enables public networking; default is true. Set false to disable it."; "<droplet-name> (required): Name for the new Droplet."; "--size (required): Droplet size slug."; "--image (required): Image ID or slug for the Droplet."; "Prerequisite: Install doctl and authenticate it with `doctl auth init`."; "Prerequisite: Creating Droplets requires the `droplet:create` scope and its listed required scopes."; "Docs conflict: The supplied v1.154.0 release note names `--public-networking`; the current doctl CLI reference (generated for v2.0.0) documents `--enable-public-networking`. The current docs do not establish the v1.154.0 flag spelling or behavior."

## doctl databases storage-autoscale get and update (doctl, 2026-06-03)
Published 2026-10-19
- slug: doctl-databases-storage-autoscale-get-and-update-a298ec9097fa
- score: 0.97

How to use it:

To inspect a database cluster’s storage autoscaling settings, run `doctl databases storage-autoscale get <cluster_uuid>`. To update them, run `doctl databases storage-autoscale update <cluster_uuid> --enabled <true|false>`; when enabling, you may also set the threshold percentage and GiB increment.

Examples:

```
doctl databases storage-autoscale get <cluster_uuid>
```

```
doctl databases storage-autoscale update <cluster_uuid> --enabled true --threshold-percent 60 --increment-gib 40
```

- why_it_matters: Inspect or update storage autoscaling options for a database cluster.
- sources: <https://github.com/digitalocean/doctl/releases/tag/v1.160.1>, <https://github.com/digitalocean/doctl/pull/1850>, <https://docs.digitalocean.com/reference/doctl/reference/databases/storage-autoscale/get/>, <https://docs.digitalocean.com/reference/doctl/reference/databases/storage-autoscale/update/>, <https://docs.digitalocean.com/reference/doctl/how-to/install/>
- gotchas: "Version: v1.160.1"; "<database-cluster-id> (required): ID of the database cluster to inspect or update."; "--enabled (required): Enable or disable storage autoscaling; value must be `true` or `false`."; "--threshold-percent: Storage usage percentage that triggers autoscaling; used when enabled. Current docs give a default of 80 when omitted."; "--increment-gib: Storage in GiB to add when autoscaling triggers; used when enabled. Current docs give a default of 10 when omitted."; "--access-token: API v2 access token; alternatively authenticate doctl with an API token."; "--api-url: Override the default API endpoint."; "Prerequisite: Install doctl and authenticate it with a DigitalOcean API token. The install guide says to create a token with read and write access."

## doctl serverless inference endpoints support (doctl, 2026-06-03)
Published 2026-10-19
- slug: doctl-serverless-inference-endpoints-support-29ce85e42aa7
- score: 0.91

How to use it:

When developing or testing code that needs model inference, use doctl’s serverless inference commands to call the endpoint. For a chat prompt, run `doctl inference chat-completions create` with a model and message, or provide a full JSON request.

Examples:

```
doctl inference chat-completions create --model <model-id> --message "<message>"
```

- why_it_matters: Call a serverless inference endpoint while developing or testing code with doctl.
- sources: <https://github.com/digitalocean/doctl/releases/tag/v1.160.1>, <https://github.com/digitalocean/doctl/pull/1846>, <https://github.com/digitalocean/doctl/blob/v1.160.1/commands/serverless_inference.go>
- gotchas: "Version: v1.160.1"; "--model (required): Model ID; required unless `--request` is set. `-m` is an alias."; "--message (required): User message; required unless `--request` is set."; "--request: Path to a JSON request body; use `-` for stdin. When set, `--model` and `--message` are not required."; "--stream: Stream output using server-sent events."; "--access-token (required): Inference credential: a Model Access Key or a DigitalOcean PAT with full access scope."; "Prerequisite: Authenticate with `--access-token` using a Gradient Model Access Key or a DigitalOcean PAT with full access; limited scopes do not work for serverless inference."; "Inference APIs require a DigitalOcean PAT with full access scope or a Gradient Model Access Key; a limited-scope PAT results in 401 for inference calls."; "Docs conflict: The current DigitalOcean CLI reference documents `doctl serverless-inference`; the v1.160.1 source documents `doctl inference` and shows the chat-completions invocation. The current reference is generated from doctl v2.0.0, so its command naming is newer than the card version."

## doctl exposes CoreDNS Autoscaler toggle for DOKS cluster create/update (doctl, 2026-06-09)
Published 2026-10-19
- slug: doctl-exposes-coredns-autoscaler-toggle-for-doks-cluster-create-update-64734330d117
- score: 0.95

How to use it:

When creating or updating a DOKS cluster, set the CoreDNS Autoscaler explicitly with `--enable-coredns-autoscaler=true` or `false`; if omitted, the API applies a Kubernetes-version-specific default. [doctl v1.161.0 source](https://github.com/digitalocean/doctl/blob/v1.161.0/commands/kubernetes.go)

Examples:

```
doctl kubernetes cluster create <cluster-name> --region <region> --version <kubernetes-version> --enable-coredns-autoscaler=true
```

```
doctl kubernetes cluster update <cluster-id-or-name> --enable-coredns-autoscaler=true
```

- why_it_matters: Create or update a DOKS cluster with the CoreDNS Autoscaler setting configured.
- sources: <https://github.com/digitalocean/doctl/releases/tag/v1.161.0>, <https://github.com/digitalocean/doctl/blob/v1.161.0/commands/kubernetes.go>, <https://docs.digitalocean.com/products/kubernetes/how-to/configure-coredns-autoscaling/>
- gotchas: "Version: v1.161.0"; "--enable-coredns-autoscaler: Boolean toggle. `true` enables CoreDNS Autoscaler; `false` disables it. If omitted, the API applies a version-specific default: true for Kubernetes 1.36.0 or later, false for older versions."; "<cluster-name> (required): Name for the cluster being created."; "<cluster-id-or-name> (required): Existing cluster identifier or name to update."; "--region: Region for the cluster; the source example supplies a region."; "--version: Kubernetes version for the cluster; the source example supplies a version."

## doctl adds NFS access point commands (doctl, 2026-07-23)
Published 2026-10-19
- slug: doctl-adds-nfs-access-point-commands-836e33eec2f8
- score: 0.97

How to use it:

When managing an NFS share access point, use `doctl nfs access-point` commands. Create one with its share ID, name, export path, and VPC ID; use `list`, `get`, or `delete` to inspect or remove access points.

Examples:

```
doctl nfs access-point create --share-id <share-id> --name <name> --path <absolute-export-path> --vpc-id <vpc-id>
```

```
doctl nfs access-point list --share-id <share-id> [--status <status>]
```

```
doctl nfs access-point get --id <access-point-id>
```

- why_it_matters: Manage an NFS access point from a coding workflow.
- sources: <https://github.com/digitalocean/doctl/releases/tag/v1.164.0>, <https://github.com/digitalocean/doctl/pull/1865>, <https://github.com/digitalocean/doctl/blob/v1.164.0/commands/nfs.go>, <https://docs.digitalocean.com/reference/doctl/reference/nfs/access-point/create/>
- gotchas: "Version: v1.164.0"; "--share-id (required): ID of the NFS share."; "--name / -n (required): Access point name."; "--path (required): Export path; must start with `/`."; "--vpc-id (required): VPC ID for the access point."; "--protocols: Allowed protocols (`NFS`, `NFS4`); default `NFS4`."; "--squash-config: Squash mode (`NO_SQUASH`, `ROOT_SQUASH`, `ALL_SQUASH`); default `ROOT_SQUASH`."; "--anonuid: Anonymous UID for squashed users; default `65534`."; "--anongid: Anonymous GID for squashed users; default `65534`."; "--identity-enforcement-enabled: Enable identity enforcement for the export; default `false`."; "--status: Optional list filter: `ACCESS_POINT_CREATING`, `ACCESS_POINT_ACTIVE`, `ACCESS_POINT_FAILED`, or `ACCESS_POINT_DELETED`."; "--id (required): Access point ID; used by `get` and `delete`."; "Prerequisite: Authenticate doctl with a DigitalOcean API access token."

## doctl databases configuration get and update support advanced_mysql (doctl, 2026-07-31)
Published 2026-10-19
- slug: doctl-databases-configuration-get-and-update-support-advanced-mysql-cf987d403b8a
- score: 0.97

How to use it:

When inspecting or changing an Advanced MySQL cluster, use `doctl databases configuration get` to retrieve its configuration or `doctl databases configuration update` to patch specified fields.

Examples:

```
doctl databases configuration get <CLUSTER_UUID> --engine advanced_mysql -o json --access-token <ACCESS_TOKEN>
```

```
doctl databases configuration update <CLUSTER_UUID> --engine advanced_mysql --config-json '{"mysql_parameters":{"max_connections":"200"}}' --access-token <ACCESS_TOKEN>
```

- why_it_matters: Inspect or update an advanced MySQL database cluster's configuration.
- sources: <https://github.com/digitalocean/doctl/releases/tag/v1.166.0>, <https://github.com/digitalocean/doctl/pull/1885>, <https://docs.digitalocean.com/reference/doctl/reference/databases/configuration/get/>, <https://docs.digitalocean.com/reference/doctl/reference/databases/configuration/update/>, <https://docs.digitalocean.com/reference/doctl/reference/auth/init/>
- gotchas: "Version: v1.166.0"; "<CLUSTER_UUID> (required): Database cluster ID in UUID format."; "--engine (required): Database engine; use `advanced_mysql` for MySQL Advanced Edition."; "-o json: Select JSON output; `--output` accepts `text` or `json`."; "--config-json (required): JSON object containing the desired cluster configuration; update is a PATCH, so unspecified fields are unchanged."; "mysql_parameters: Nested configuration object shown in the release-note example; official docs read here do not document its sub-keys or mutual exclusivity."; "--access-token: API v2 access token; doctl can instead use initialized authentication."; "Prerequisite: Install doctl and authenticate with a DigitalOcean API token; alternatively provide `--access-token` on each command."

## doctl adds GradientAI simulation APIs (doctl, 2026-08-31)
Published 2026-10-19
- slug: doctl-adds-gradientai-simulation-apis-37bc9fe2a74d
- score: 0.95

How to use it:

When working with GradientAI scenarios or simulations in doctl v1.168.0, choose the command for the operation: use `scenario-set` to manage scenario sets and `simulation-run` to run or inspect simulations.

Examples:

```
doctl gradient scenario-set list --statuses ready
```

```
doctl gradient simulation-run list --statuses running
```

```
doctl gradient simulation-run get <run-uuid> -o json
```

- why_it_matters: When working with GradientAI scenarios or simulations through doctl, inspect the added simulation API commands and use the command that matches the operation you need.
- sources: <https://github.com/digitalocean/doctl/releases/tag/v1.168.0>, <https://github.com/digitalocean/doctl/pull/1937>, <https://docs.digitalocean.com/reference/doctl/reference/gradient/scenario-set/list/>, <https://docs.digitalocean.com/reference/doctl/reference/gradient/simulation-run/list/>, <https://docs.digitalocean.com/reference/doctl/reference/gradient/simulation-run/get/>
- gotchas: "Version: v1.168.0"; "`<run-uuid>` (required): UUID of the simulation run to retrieve."; "`--statuses`: Filters runs by status; documented values include `running`."; "`-o json`: Selects JSON output; the get command documentation says this also shows per-scenario results."; "Prerequisite: Authenticate doctl with a DigitalOcean API V2 access token; the command reference lists `--access-token` / `-t` as a global flag."

Next: https://sincecutoff.com/v1/changes.md?tool=doctl&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxNjg0LCJzaW5jZSI6bnVsbCwidG9vbCI6ImRvY3RsIiwidiI6MX0
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->