<!– Automatically generated by Pandoc –> ." Automatically generated by Pandoc 3.1.8 ." .TH “gemstash-authorize” “1” “October 9, 2015” “” “” .SH Name gemstash-authorize - Adds or removes authorization to interact with privately stored gems .SH Synopsis f[CR]gemstash authorize [permissions] [–remove] [–list] [–key SECURE_KEY] [–name NAME] [–config-file FILE]f .SH Description Adds or removes authorization to interact with privately stored gems. .PP Any arguments will be used as specific permissions. Valid permissions include f[CR]pushf[R], f[CR]yankf[R], and f[CR]fetchf[R]. If no permissions are provided, then all permissions will be granted (including any that may be added in future versions of Gemstash
). .SS Usage .IP .EX gemstash authorize gemstash authorize push yank gemstash authorize push –name my-auth gemstash authorize yank –key <secure-key> gemstash authorize –remove –key <secure-key> gemstash authorize –list .EE .SH Options .IP [bu] 2 f[CR]–config-file FILEf: Specify the config file to use. If you arent using the default config file at f[CR][ti]/.gemstash/config.ymlf or f[CR][ti]/.gemstash/config.yml.erbf, then you must specify the config file via this option. .IP [bu] 2 f[CR]–key SECURE_KEYf: Specify the API key to affect. This should be the actual key value, not a name. This option is required when using f[CR]–removef but is optional otherwise. If adding an authorization, using this will either create or update the permissions for the specified API key. If missing, a new API key will always be generated. Note that a key can only have a maximum length of 255 chars. .IP [bu] 2 f[CR]–namef: Name of the authorization. Purely for ease of identification, not required. .IP [bu] 2 f[CR]–removef: Remove an authorization rather than add or update one. When removing, permission values are not allowed. The f[CR]–key <secure-key>f option is required. .IP [bu] 2 f[CR]–listf: List current authorizations. Provide f[CR]–namef or f[CR]–keyf to show only one result.