Version: 0.7

kore exchange

kore exchange#

Exchanges a robot token for a short-lived access token

Synopsis#

Robot tokens by default in Kore by themselves do not grant access to the resources, they are exchanged for short-lived access tokens (by default these have a 30min expiration). Once exchanged you can use the access tokens as authorization to access resources.

kore exchange [flags]

Examples#

# Exchange a robot token for a short-lived access token
$ kore exchange
# You can source the access token
$ source <(kore exchange)
# Request the age of the access token for 1day (dependent on kore policies)
$ kore exchange --expires 24h
# Write the environments variables to a file (KORE_SERVER, KORE_TEAM and KORE_TOKEN)
$ kore exchange --env-file <path>
$ source ./<path>
# We be using the session token now
$ kore <commands>

Options#

--env-file writes session token and environment variables to file
--expires duration expiration of the access token (default 30m0s)
-h, --help help for exchange

Options inherited from parent commands#

--debug indicates we should use debug / trace logging (defaults: false)
--force is used to force an operation to happen (defaults: false)
--no-wait indicates if we should wait for resources to provision
-o, --output string the output format of the resource (json,yaml,table,template) (default "table")
--profile string allows you to explicitly set the selected profile
--show-headers indicates we should display headers on table out (default true)
-t, --team string the team you are operating within
--verbose enables verbose logging for debugging purposes (defaults: false)

SEE ALSO#

  • kore - kore provides a cli for the Kore