Skip to content

Implement create admin token for root user in GitLab component

James Nutt requested to merge add-token-seed-step into master

What does this MR do and why?

First iteration for https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/1291, also as a follow-up for https://gitlab.com/gitlab-org/gitlab-qa/-/merge_requests/896#note_915838550

  • Add a script to create admin token for root user
  • Add a step in Component::GitLab for creating admin token
  • Move seed-db logic on instance level for flexibility
  • Add runner option for --no-admin-token

Added env variable GITLAB_QA_ADMIN_ACCESS_TOKEN in CI settings

Screenshots or screen recordings

Pipeline result

Waiting for GitLab at `https://docker/help` to become available 200 -> GitLab is available.
[date=2022-05-06 11:50:34 from=Gitlab QA] INFO  -- Docker shell command: `docker cp /builds/gitlab-org/gitlab-qa/support/data gitlab:/tmp/data-seeds`
[date=2022-05-06 11:50:35 from=Gitlab QA] INFO  -- Docker shell command: `docker exec gitlab bash -c "gitlab-rails runner /tmp/data-seeds/admin_access_token_seed.rb"`
Personal access token seeded for root user.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by James Nutt

Merge request reports