blossom location:update
Set a Location's maximum capacity and BYOC Server sizes
Set a Location’s maximum capacity and BYOC Server sizes
Usage
blossom location:update --id ID [--data DATA]
Flags
| Flag | Description |
|---|---|
--id (required) |
Location id |
--data, -d |
YAML or JSON data, a path to a data file, or an HTTP(S) URL |
Set a Location’s name, maximum capacity and, on Blossom BYOC, the Server sizes Blossom may create on your provider bill:
blossom location:server_sizes --id location-100
blossom location:update --id location-100 --data location.yml
location:
# Shown first wherever you pick a Location. Blank for a name from the
# provider and region, like "Hetzner Falkenstein".
name: Production EU
# The workload maximum, excluding Builders, in capacity units (2 vCPU / 4 GB each).
# Leave it blank for this Location's approved ceiling; it can't be higher.
maximum_unit_count: 4
# The CPU type every Server here uses: arm or x86. New Locations take
# it from the Account (Auto prefers ARM where offered). It can change
# only while nothing runs here.
arch: arm
# Blossom BYOC only. Blossom picks among these for each workload, all of
# the Location's CPU type.
allowed_server_sizes:
- cax11
- cax21
Omit a setting to keep it. A deploy above the maximum waits; nothing already
running stops. A size change applies to the next Server Blossom creates.
Set reserved capacity and idle retention with capacity:update.