---
title: blossom cloud_provider:update
url: "/docs/reference/cli/cloud_provider/update/"
canonical_url: https://docs.blossom88.com/docs/reference/cli/cloud_provider/update/
markdown_url: https://docs.blossom88.com/docs/reference/cli/cloud_provider/update.md
summary: Update a cloud provider
categories:
- cli
- reference
---

# blossom cloud_provider:update

Update a cloud provider

## Usage

    blossom cloud_provider:update --id ID [--data DATA]

## Flags

| Flag | Description |
| --- | --- |
| `--id (required)` | Cloud provider id |
| `--data, -d` | YAML or JSON data, a path to a data file, or an HTTP(S) URL |

Examples:

    blossom cloud_provider:update --id cloud_provider-100 --data cloud_provider.yml
    blossom cloud_provider:update --id cloud_provider-100 -d '{"cloud_provider":{"name":"production"}}'

cloud_provider.yml:

```yaml
cloud_provider:
  name: production
```

Updates a cloud provider in the current Blossom Account. `--id` identifies the
existing cloud provider. Mutable fields live under `cloud_provider` in `--data`.
The provider type is immutable; omit `cloud_provider.provider` from update data.

Local files and inline data support `$VAR` and `${VAR}` substitution from
`.env`, `BLOSSOM_VARS_FILE`, and the process environment. See
`blossom help:data`.

Do not include `cloud_provider.id` in the data file. The id belongs in `--id`;
the payload contains the fields to change.

After updating credentials, check the provider:

    blossom cloud_provider:check --id cloud_provider-100