exo(1)

πŸ“¦
version 1.102.1 Β· 2 versions
, in nixpkgs unstable

πŸ’… exo(1) β€” the exo manual, bestie edition πŸŽ€

okay so real talk, this is page one of the exo manual, and today we're deep-diving one very specific little command. buckle up πŸ¦‹


✨ NAME ✨

exo-dbaas-external-endpoint-update β€” bestie, it literally updates an existing external endpoint for DBaaS. that's the whole vibe. πŸ’–


🌸 SYNOPSIS 🌸

exo dbaas external-endpoint update TYPE ID [flags]

like, you give it a TYPE, you give it an ID, you toss in some [flags] if you're feeling spicy, and it goes and updates the thing. iconic behavior honestly.


πŸ¦‹ DESCRIPTION πŸ¦‹

Update an existing external endpoint for DBaaS.

that's it. that's the whole description. short, sweet, main character energy. no cap. ✨


πŸŽ€ OPTIONS πŸŽ€

okay so here's where it gets juicy. every single flag, accounted for, no gatekeeping:

  • -h, --help[=false] β€” help for update. your little "wait what does this do again" safety net 🫢
  • --help-datadog[=false] β€” show usage for flags specific to the datadog external endpoint type. datadog girlies, this one's for you πŸ•
  • --help-elasticsearch[=false] β€” show usage for flags specific to the elasticsearch external endpoint type. elasticsearch stans rise πŸ”
  • --help-opensearch[=false] β€” show usage for flags specific to the opensearch external endpoint type. open search, open heart, open flags πŸ’œ
  • --help-prometheus[=false] β€” show usage for flags specific to the prometheus external endpoint type. fire flag for a fire name πŸ”₯
  • --help-rsyslog[=false] β€” show usage for flags specific to the rsyslog external endpoint type. the syslog classic, we love her 🌈
ngl the pattern is kinda slay: every endpoint type gets its own --help-* flag so you can peek at the flags that actually apply to your type instead of drowning in all of them. iykyk. πŸ’…

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

these bad boys come free from the parent command, so you don't declare them yourself, you just have them. royalty behavior honestly:

  • -C, --config="" β€” Specify an alternate config file [env EXOSCALE_CONFIG]. default is empty string, so it falls back on the usual config. πŸ’–
  • -O, --output-format="" β€” Output format (table|json|text), see exo output --help for more information. pick your aesthetic ✨
  • --output-template="" β€” Template to use if output format is "text". yes, you can customize it. yes, that's hot. πŸŽ€
  • -Q, --quiet[=false] β€” Quiet mode (disable non-essential command output). for when you want peace and quiet, fr fr 🀫
  • --timeout=15s β€” Per-zone timeout for list operations; -1s disables timeout [env EXOSCALE_TIMEOUT]. default is 15s, and -1s means no timeout at all β€” use that one with intention, bestie πŸ’€
  • -A, --use-account="" β€” Account to use in config file [env EXOSCALE_ACCOUNT]. default empty string 🫢

🌈 SEE ALSO 🌈


⭐ HISTORY ⭐

  • 1-Jan-1980 β€” Auto generated by spf13/cobra

yeah she's an auto-generated baby from way back, and honestly? she's thriving. πŸ“


πŸ’€ tiny reminder bestie: this page is literally labeled "Auto generated by spf13/cobra", so if something looks weird, blame the cobra, not me. πŸ™ˆ

okay that's the page!! this has been the exo(1) manual, auto generated by spf13/cobra, dated Jan 1980, and yes the footer really does say exactly that. love that for us. mwah πŸ’‹πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from