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

# blossom service:update

Update a service

## Usage

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

## Flags

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

Examples:

    blossom service:update --id service-100 --data service.yml

service.yml:

```yaml
service:
  health_check:
    enabled: true
    kind: http
    path: /ready
    traffic: true
```

Changes to a Service health check wait for the next Environment deployment.

To send a path such as `/cable` to this Service instead of `web`, add a route
with `blossom route:create`; routes belong to the Environment.

Persistent storage grows through the same `storage` object as creation. Include
its existing mount path and availability; neither can change. Storage cannot
shrink. Growth starts on save and is reported by its Activity. Stop existing
Containers before adding storage to a stateless Service.

After retaining a Volume, set `enabled: true`, then use
`service:scale --id SERVICE_ID --desired-size 1 --follow` to resume its last
successful Release without redeploying neighboring Services.
Changing a Persistent Service's Container resources
requires retiring its compute with `service:delete --storage retain` first.