docs: fix eventing gitlab source readme (#5598)

* docs: fix gitlab webhook breadcrumb in gitlab eventing readme

* docs: use project access token for gitlab source in gitlab eventing readme

from security perspective it's better to use project access token instead of personal access token
This commit is contained in:
Arkadius Jonczek 2023-06-23 12:10:36 +02:00 committed by GitHub
parent 07d5949833
commit 225a69b10f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

View File

@ -74,7 +74,7 @@ kubectl -n default apply -f event-display.yaml
### Create GitLab Tokens ### Create GitLab Tokens
1. Create a 1. Create a
[personal access token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html) [project access token](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html)
which the GitLab source will use to register webhooks with the GitLab API. which the GitLab source will use to register webhooks with the GitLab API.
The token must have an "api" access scope in order to create repository The token must have an "api" access scope in order to create repository
webhooks. Also decide on a secret token that your source will use to webhooks. Also decide on a secret token that your source will use to
@ -153,7 +153,7 @@ kubectl -n default apply -f event-display.yaml
### Verify ### Verify
Verify that GitLab webhook was created by looking at the list of webhooks under Verify that GitLab webhook was created by looking at the list of webhooks under
**Settings >> Integrations** in your GitLab project. A hook should be listed **Settings >> Webhooks** in your GitLab project. A hook should be listed
that points to your Knative cluster. that points to your Knative cluster.
Create a push event and check the logs of the Pod backing the Create a push event and check the logs of the Pod backing the