divekit credentials

Synopsis

Manage the project access tokens that Divekit issues for a distribution.

When Divekit links a work repository and its evaluation repository, it creates project access tokens and stores them as CI/CD variables of the repository that uses them. GitLab ends such a token on its expiry date and mails the members of the owning project beforehand. These commands show, renew and revoke exactly those tokens.

Divekit manages the tokens whose name it derives from a link: divekit-link-<target>, divekit-<target>-api and the legacy name divekit-access-token. Every other project access token is left alone, so a token a student created is never touched.

The personal token that the CLI itself uses belongs to ‘divekit auth’.

Usage

divekit credentials [flags]

Examples

# Which credentials expire soon?
divekit credentials status -d ST2M4

# Renew every credential for another six months
divekit credentials renew -d ST2M4 --lifetime 6mo

# Remove the credentials of one repository
divekit credentials revoke -d ST2M4 --uuid abc123

Inherited Flags

-l, --loglevel string   log level (debug, info, warn, error, fatal) (default "info")
      --no-index          skip project index update
      --non-interactive   run in non-interactive mode (fails if interactive input is required)
  -y, --yes               assume yes/default for all prompts (non-interactive with automatic defaults)

Available Subcommands

• renew — Replace the managed tokens of a distribution before they expire
• revoke — Revoke the managed tokens of a distribution and remove their variables
• status — Report the managed credentials of a distribution