exo(1)

📦
version 1.102.1 · 2 versions
, in nixpkgs unstable

💅 exo(1) — the one where you update an Instance Pool

okay bestie, welcome to exo(1) — well, technically this page is all about one command from the exo manual, and it's the glow-up command for your Instance Pools. sit down, hydrate, let's go 🫶

✨ NAME ✨

exo-compute-instance-pool-update — Update an Instance Pool

like, literally, it updates an Instance Pool. that's the whole vibe. iconic.

🦋 SYNOPSIS 🦋

exo compute instance-pool update NAME|ID [flags]

you give it a pool by NAME or ID, you sprinkle your flags, you slay. periodt.

🌸 DESCRIPTION 🌸

This command updates an Instance Pool. that's it, that's the main character moment ✨

and here's the fun part — the supported output template annotations you can use (copy these exactly, bestie, don't freestyle the capitalization):

.ID, .Name, .Description, .InstanceType, .Template, .Zone, .AntiAffinityGroups, .SecurityGroups, .PrivateNetworks, .ElasticIPs, .IPv6, .PublicIPAssignment, .SSHKey, .Size, .DiskSize, .InstancePrefix, .State, .Labels, .Instances

ngl, that list is giving "wear your name on your jacket" energy. use them in your templates, iykyk 💅

🎀 OPTIONS 🎀

  • -a, --anti-affinity-group=[] — the managed Compute instances Anti-Affinity Group NAME|ID (you can specify this multiple times, go off)
  • -c, --cloud-init="" — path to the cloud-init user data configuration file
  • --cloud-init-compress[=false] — compress the instance cloud-init user data
  • --deploy-target="" — the managed Compute instances Deploy Target NAME|ID
  • --description="" — Instance Pool description
  • --disk-size=0 — managed Compute instances disk size
  • -e, --elastic-ip=[] — managed Compute instances Elastic IP ADDRESS|ID (can be specified multiple times, yes queen, stacking is allowed)
  • -h, --help[=false] — help for update
  • --instance-prefix="" — string to prefix managed Compute instances names with
  • --instance-type="" — managed Compute instances type (format: [FAMILY.]SIZE)
  • -6, --ipv6[=false] — enable IPv6 on managed Compute instances
  • --label=[] — Instance Pool label (format: key=value)
  • --min-available=0 — Minimum number of running Instances
  • -n, --name="" — Instance Pool name
  • --private-network=[] — managed Compute instances Private Network NAME|ID (can be specified multiple times)
  • -s, --security-group=[] — managed Compute instances Security Group NAME|ID (can be specified multiple times)
  • --ssh-key="" — SSH key to deploy on managed Compute instances
  • -t, --template="" — managed Compute instances template NAME|ID
  • --template-visibility="public" — instance template visibility (public|private)
  • -z, --zone="" — Instance Pool zone

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the heirlooms, the hand-me-downs, the family recipes 👑

  • -C, --config="" — Specify an alternate config file [env EXOSCALE_CONFIG]
  • -O, --output-format="" — Output format (table|json|text), see exo output --help for more information
  • --output-template="" — Template to use if output format is text
  • -Q, --quiet[=false] — Quiet mode (disable non-essential command output)
  • --timeout=15s — Per-zone timeout for list operations; -1s disables timeout [env EXOSCALE_TIMEOUT]
  • -A, --use-account="" — Account to use in config file [env EXOSCALE_ACCOUNT]
ok lowkey important: --timeout defaults to 15s, and -1s is the "no timeout, we die like legends" option. and yes, those env vars are real, don't ignore them 💀

🔥 SEE ALSO 🔥

💜 HISTORY 💜

1-Jan-1980 — Auto generated by spf13/cobra

and that's the page, bestie!! 🎀 it was Auto generated by spf13/cobra, stamped Jan 1980, sitting all cozy under exo(1) — go update that pool and be the main character of your own cloud ✨💅🦋

📦 where this page comes from