Proposed CLI commands

[christiansmith]

login
logout

issuer:select
issuer:create
issuer:list
issuer:get
issuer:update
issuer:delete
issuer:replicate <target>

user:register
user:list [size [page]]
user:info <uuid | email>
user:providers <uuid | email>
user:provider <uuid | email> <provider>
user:update <uuid | email> [key value]
user:remove <uuid | email>
user:assign <uuid | email> <role>
user:revoke <uuid | email> <role>
user:access_token  <uuid | email> <scope> [<scope> [...]]
user:auth <uuid | email>                                // complete id_token token auth response
user:suspend
user:reinstate

client:register
client:list [size [page]]
client:info <uuid | uri>
client:update <uuid | uri> [key value]
client:delete <uuid | uri>
client:assign <uuid | uri> <role>
client:revoke <uuid | uri> <role>
client:token  <uuid | uri> <scope> [<scope> [...]]

scope:list
scope:get <scope>
scope:create <scope> <description>
scope:update <scope> [key value]
scope:delete <scope>

role:list
role:get
role:create
role:update
role:delete
role:permit <role> <scope>
role:forbid <role> <scope>

keys:generate
keys:rotate
keys:public --copy
keys:jwks --copy

uri:authorize
uri:connect
uri:signin

init:heroku
init:modulus
init:digitalocean
init:amazon
init:joyent
init:triton
init:flynn
init:deis

push/deploy

monitor
log:search
config
status

[christiansmith]

We could try making providers a proper resource instead of just config file settings. Then the CLI/HTTP API could be used to configure them remotely without having to restart the server.

provider:list
provider:get <name>
provider:create
provider:update <name>
provider:delete <name>
provider:enable <name>
provider:disable <name>

[adalinesimonian]

+1,000,000 for dynamically configurable providers/protocols

[adalinesimonian]

From anvilconnect/connect#34:

christiansmith:

The cli tool has subcommands, similar to git or npm, and should support command-specific help.

$ nv assign --help