exo(1)

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

πŸŽ€ exo(1) β€” storage cors, but make it iconic πŸŽ€

✨ NAME ✨

exo-storage-cors β€” manage buckets CORS configuration. That's the whole vibe: bucket CORS-config management, and yes bestie, we're getting into it. πŸ’…

πŸ› οΈ SYNOPSIS πŸ› οΈ

exo storage cors [flags]

🌸 DESCRIPTION 🌸

Okay so these commands are how you manage the CORS configuration of a bucket. Literally the bucket's CORS-config situation. ✨

For more information on CORS, please refer to the Exoscale Storage documentation:

https://community.exoscale.com/documentation/storage/cors/

Notes, and listen up:

  • ⚠️ It is not possible to edit a CORS configuration rule once it's been created, nor to delete rules individually -- the whole configuration must be reset using the exo storage cors reset command.

πŸŽ€ OPTIONS πŸŽ€

  • -h, --help[=false] β€” help for cors. No cap, that's the one option here. 🫢

🧬 OPTIONS INHERITED FROM PARENT COMMANDS 🧬

These are the inherited flags, bestie β€” they come from the parent commands. πŸ’–

  • -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]. πŸ‘‘

πŸ‘€ SEE ALSO πŸ‘€

πŸ“œ HISTORY πŸ“œ

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

🌈 That's the whole page, bestie β€” Auto generated by spf13/cobra, Jan 1980, for exo(1). Mwah πŸ’‹ πŸŽ€

πŸ“¦ where this page comes from