Commit 9ecff6b3 authored by Ulises Fierro's avatar Ulises Fierro Committed by Marcel Amirault

Added more information regarding CI_JOB_TOKEN

Clarifies what "user that executes the job" previously implied
parent a2aa5348
...@@ -24,7 +24,10 @@ You can use a GitLab CI/CD job token to authenticate with specific API endpoints ...@@ -24,7 +24,10 @@ You can use a GitLab CI/CD job token to authenticate with specific API endpoints
- [Terraform plan](../../user/infrastructure/index.md). - [Terraform plan](../../user/infrastructure/index.md).
The token has the same permissions to access the API as the user that executes the The token has the same permissions to access the API as the user that executes the
job. Therefore, this user must be assigned to [a role that has the required privileges](../../user/permissions.md#gitlab-cicd-permissions). The token has the same permissions to access the API as the user that caused the
job to run. A user can cause a job to run by pushing a commit, triggering a manual job,
being the owner of a scheduled pipeline, and so on. Therefore, this user must be assigned to
[a role that has the required privileges](../../user/permissions.md#gitlab-cicd-permissions).
The token is valid only while the pipeline job runs. After the job finishes, you can't The token is valid only while the pipeline job runs. After the job finishes, you can't
use the token anymore. use the token anymore.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment