Skip to content

Commit

Permalink
chore(docs): Fix incorrect base_url in gitlab/config (#13)
Browse files Browse the repository at this point in the history
* add https to base_url

* Update README.md
  • Loading branch information
FalcoSuessgott committed Sep 19, 2023
1 parent d4d4dae commit 4bb7b71
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,16 +59,19 @@ Since Gitlab 16.0 the ability to create non expiring token has been removed.
The command bellow will set up the config backend with a max TTL of 48h.

```shell
$ vault write gitlab/config max_ttl=48h base_url=gitlab.example.com token=gitlab-super-secret-token
$ vault write gitlab/config max_ttl=48h base_url=https://gitlab.example.com token=gitlab-super-secret-token
```

### Roles

This will create three roles, one of each type.

```shell
# personal access tokens can only be created by Gitlab Administrators (see https://docs.gitlab.com/ee/api/users.html#create-a-personal-access-token)
$ vault write gitlab/roles/personal name=personal-token-name path=username scopes="read_api" token_type=personal token_ttl=24h

$ vault write gitlab/roles/project name=project-token-name path=group/project scopes="read_api" access_level=guest token_type=project token_ttl=24h

$ vault write gitlab/roles/group name=group-token-name path=group/subgroup scopes="read_api" access_level=developer token_type=group token_ttl=24h
```

Expand Down

0 comments on commit 4bb7b71

Please sign in to comment.