exo(1)

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

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

Okay so this is the manual page for exo β€” specifically the exo-iam-role-create command, which lives in the exo man page family. Yes the page is named exo(1) and the command is exo-iam-role-create. It's giving "folder named after the assignment." Anyway. Let's go ✨


🌸 NAME 🌸

exo-iam-role-create β€” literally creates an IAM Role. That's the whole vibe. πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

exo iam role create NAME [flags]

You give it a NAME, you give it some [flags], it gives you a role. Iconic. πŸ’…


✨ DESCRIPTION ✨

So this command creates a brand-new IAM Role, no cap. 🫢

And here's the cute part: if you want to read the Policy from STDIN, you just append - to the --policy flag. That's it. That's the trick. πŸ’–

Pro Tip (and I mean pro pro tip, this one ate): you can reuse an existing role policy by feeding the output of the show command straight into it as input:

exo iam role show --policy --output-format json <role-name> | exo iam role create <new-role-name> --policy -

Look at that pipe. Look at it. Main character energy fr fr. 🌈

Supported output template annotations, and yes you need all of them: .ID, .Name, .Description, .Editable, .Labels, .Permissions, .Policy


πŸ’œ OPTIONS πŸ’œ

  • --description="" β€” the role description. Give your role a little personality. πŸ’¬
  • --editable[=true] β€” set --editable=false to prevent editing the Policy after creation. Locked in. πŸ”’ (yes, "do prevent" is what the original says, it's a whole mood, I'm not touching it)
  • -h, --help[=false] β€” help for create. When in doubt, ask for help. Self-care. πŸŽ€
  • --label=[] β€” role labels, format is key=value. 🏷️
  • --permissions=[] β€” role permissions. The actual powers. ⚑
  • --policy="" β€” role policy (use - to read from STDIN). πŸ“

🌟 OPTIONS INHERITED FROM PARENT COMMANDS 🌟

These are the family hand-me-downs, and honestly they're all bangers:

  • -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). Shhh. 🀫
  • --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 🫢

  • exo-iam-role(1) β€” go read the parent page, it's the source of all this lore πŸ’–

πŸ“œ HISTORY πŸ“œ

1-Jan-1980 β€” Auto generated by spf13/cobra. The cobra did all the work and honestly? Respect. 🐍


Lowkey the most important part: this whole page is Auto generated by spf13/cobra, and it's dated Jan 1980 β€” which is before most of us were born but the vibes are timeless. πŸ’€βœ¨

That's the whole page, bestie β€” role created, policy piped, flags inherited, nothing skipped. Slay. πŸ’…πŸŽ€

πŸ“¦ where this page comes from