Right now, it takes a few steps to reserve a board and access it. The user has to request a token, set it in the environment, and then continue. The requested token is long lived (see issue #1).
A better ideal flow would allow the user to run a command which would setup the environment necessary to reserve and access boards and launch a shell, then when the shell exits, the token will be revoked.
Right now, it takes a few steps to reserve a board and access it. The user has to request a token, set it in the environment, and then continue. The requested token is long lived (see issue #1).
A better ideal flow would allow the user to run a command which would setup the environment necessary to reserve and access boards and launch a shell, then when the shell exits, the token will be revoked.
Right now, it takes a few steps to reserve a board and access it. The user has to request a token, set it in the environment, and then continue. The requested token is long lived (see issue #1).
A better ideal flow would allow the user to run a command which would setup the environment necessary to reserve and access boards and launch a shell, then when the shell exits, the token will be revoked.