Documentation: Programatically creating a personal access token
What does this MR do?
While working on a https://github.com/terraform-providers/terraform-provider-gitlab/pull/282 I (re)discovered a use case for programmatically creating a predefined personal access token.
This is useful for people who are running automation or tests against a GitLab test environment. There could be other applications used directly on a production GitLab environment, but I am doubtful this would be practical due to security concerns.
Related issues
Closes gitlab-com/support/toolbox/snippets#25 (closed) gitlab-com/support/toolbox/snippets#24 (closed) #213255 (closed)
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
If applicable, update the permissions table. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖