4mgemstash-authorize24m(1) 4mgemstash-authorize24m(1)
<!– Automatically generated by Pandoc –>
1mName0m
gemstash-authorize - Adds or removes authorization to interact with privately stored gems
1mSynopsis0m
gemstash authorize [permissions] [--remove] [--list] [--key SECURE_KEY] [--name NAME] [--config-file FILE]
1mDescription0m
Adds or removes authorization to interact with privately stored gems. Any arguments will be used as specific permissions. Valid permissions include push, yank, and fetch. If no permissions are provided, then all permissions will be granted (including any that may be added in fu- ture versions of Gemstash). 1mUsage0m 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
1mOptions0m
o --config-file FILE: Specify the config file to use. If you aren't using the default config file at ~/.gemstash/config.yml or ~/.gem- stash/config.yml.erb, then you must specify the config file via this option. o --key SECURE_KEY: Specify the API key to affect. This should be the actual key value, not a name. This option is required when using --remove but is optional otherwise. If adding an authorization, us- ing this will either create or update the permissions for the speci- fied 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. o --name: Name of the authorization. Purely for ease of identifica- tion, not required. o --remove: Remove an authorization rather than add or update one. When removing, permission values are not allowed. The --key <secure- key> option is required. o --list: List current authorizations. Provide --name or --key to show only one result. October 9, 2015 4mgemstash-authorize24m(1)