Edit icon Edit This Page

Manage personal access tokens and deploy tokens

Manage the two kinds of token of Repsy.

personal access token (PAT)  bound to YOUR USER. It signs panel API calls (and
rp itself) with the scopes you give it, whatever
the repository. This is what rp commands without
--repo manage. Managing them works with the
browser sign-in of rp auth login or with a
personal access token (also in REPSY_TOKEN)
that holds the scopes involved (RPS-2440).
deploy token                 bound to ONE REPOSITORY. It is a username and
token pair for package clients (npm, Maven,
Docker, ...) to push or pull in that repository
only. It cannot call the panel API. These are the
commands with --repo <name>.

A new secret is shown ONCE, when it is created (or rotated). rp prints it on stdout only when you ask for it with –show-secret or with a structured –output (json, yaml or –jq), and refuses to create the token otherwise so the secret is not lost. A secret is never read from a flag, because that would put it in your shell history. A list never contains a secret.

rp token

Options inherited from parent commands

      --api-url string           Panel API URL of the profile, overrides the stored value
      --ca-file string           PEM file with extra trusted CA certificates
      --debug                    Print debug output with secrets redacted
      --hostname string          Repsy host to use instead of the current profile
      --insecure                 Do not verify TLS certificates (unsafe; plain http is chosen with the URL, not with this flag)
      --insecure-storage         Keep credentials in a plain 0600 file instead of the OS keyring (unsafe; a warning is printed once per command)
      --jq string                Filter JSON output with a jq expression (implies --output json)
      --no-color                 Disable colored output
      --no-input                 Never prompt; fail when input is needed
      --output table|json|yaml   Output format: table, json or yaml (default table; json when --jq is given)
      --owner string             Owner segment of Cloud protocol URLs; --owner= means none
      --registry-url string      Protocol host URL of the profile, overrides the stored value
      --type os|cloud            Product of the host, overrides detection
      --web-url string           Panel UI URL of the profile (where /cli/auth lives), overrides the stored value
      --yes                      Answer yes to confirmation prompts

See also

  • rp - Command line client for Repsy OS and Repsy Cloud
  • rp token create - Create a personal access token, or a deploy token with –repo
  • rp token list - List your personal access tokens, or the deploy tokens of a repository
  • rp token revoke - Revoke a personal access token, or a deploy token with –repo
  • rp token rotate - Replace the secret of a personal access token, or of a deploy token with –repo
Found a problem with this page?