divekit access revoke

Remove users from the repositories of a distribution

Synopsis

Remove the direct membership of one or more GitLab users from the repositories of a distribution.

Without –target and –uuid every work and evaluation repository is affected. A repository the user is no member of stays unchanged, so the command can be repeated safely.

A user can also reach a repository through a membership of a parent group, for example when someone added them to the group in GitLab. Divekit never changes groups, so it checks every repository after the removal and names the ones the user can still reach, together with the role the group grants. Remove that membership in GitLab.

The plan needs confirmation; –dry-run stops after the plan and –yes confirms without a prompt.

Usage

divekit access revoke <username>... [flags]

Examples

# Remove a supervisor from every repository
divekit access revoke -d ST2M4 manuel

# Remove a tester from one repository
divekit access revoke -d ST2M4 maren --uuid 123e4567-e89b-12d3-a456-426614174000

Flags

-d, --distribution string   Distribution name
  -n, --dry-run               Show the plan without changing anything
  -r, --remote string         Remote repository URL (e.g. GitLab instance)
      --target strings        Only repositories of this target, for example work or eval (repeatable)
  -t, --token string          GitLab token or token file path (file:///...)
      --uuid strings          Only repositories with these UUIDs (repeatable or comma-separated)

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)

Parent Command

divekit access