CLOUDSTACK(1)

✨ NAME ✨

okay so bestie, welcome to cloudstack β€” the command-line client for Apache CloudStack. that's the whole vibe, that's the moment, that's what we're doing here πŸ’… (and yeah, it's the CLOUDSTACK(1) page, General Commands Manual energy, we been knew ✨)


πŸ¦‹ SYNOPSIS πŸ¦‹

cloudstack [--async] command [option=value ...]

that's it. that's the whole spell. go off πŸ‘‘


🌸 DESCRIPTION 🌸

so like, cloudstack is a command-line client for Apache CloudStack, periodt. the command you pass in should be the name of an API command β€” that's the assignment, that's the whole task, no cap. and then cloudstack hands you back the result as JSON-formatted output, which is honestly iconic, we love a machine-readable slay 🌈

πŸŽ€ where the config lives (read it, it matters) πŸŽ€

Configuration gets read from several locations, and the order is very much a thing β€” it goes like this:

  1. the CLOUDSTACK_ENDPOINT, CLOUDSTACK_KEY and CLOUDSTACK_SECRET environment variables 🌱
  2. a CLOUDSTACK_CONFIG environment variable pointing to an .ini file πŸ“‚
  3. a cloudstack.ini file in the current working directory πŸ“
  4. a .cloudstack.ini file in the home directory 🏠
fr fr, that order is the order β€” first one wins, so don't come crying to me when your env vars are lowkey overriding your ini file πŸ’€

🫢 SEE ALSO 🫢

want more lore? more deep-dive, more main character documentation? bestie, go look at the documentation of the CloudStack API at:

http://cloudstack.apache.org/docs/api/

that's the plug, iykyk πŸ”₯


and that's the page!! this beauty is from Debian, dated August 18, 2013, and it's the CLOUDSTACK(1) manual β€” so go forth, run your API commands, read your configs in the right order, and slay πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ‘‘

πŸ“¦ where this page comes from