You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -92,7 +94,7 @@ The current authentication model requires providing Vault with a Gitlab Token.
92
94
| base_url | yes | n/a | no | The address to access Gitlab |
93
95
| auto_rotate_token | no | no | no | Should we autorotate the token when it's close to expiry? (Experimental) |
94
96
| auto_rotate_before | no | 24h | no | How much time should be remaining on the token validity before we should rotate it? Minimum can be set to 24h and maximum to 730h |
95
-
| type | yes | n/a | no | The type of gitlab instance that we use can be one of saas, self-managed or dedicated |
97
+
| type | yes | n/a | no | The type of gitlab instance that we use can be one of saas, self-managed or dedicated |
96
98
97
99
### Role
98
100
@@ -105,11 +107,41 @@ The current authentication model requires providing Vault with a Gitlab Token.
105
107
| scopes | no | [] | no | List of scopes |
106
108
| token_type | yes | n/a | no | Access token type |
107
109
| gitlab_revokes_token | no | no | no | Gitlab revokes the token when it's time. Vault will not revoke the token when the lease expires |
108
-
| config_name | no | default | no | The configuration to use for the role |
110
+
| config_name | no | default | no | The configuration to use for the role |
109
111
110
112
#### path
111
113
112
-
If `token_type` is `group-service-account` then the format of the path is `{groupId}/{serviceAccountName}` example `265/service_account_65c74d39b4f71fc3fdc72330fce28c28`.
114
+
##### `token_type` is `personal`
115
+
116
+
Format of the path is `{username}` example `admin`.
117
+
118
+
##### `token_type` is `project`
119
+
120
+
Format of the path is the full path of the project for example `group/project` or `group/subgroup/project`
121
+
122
+
##### `token_type` is `group`
123
+
124
+
Format of the path is the full path of the project for example `group` or `group/subgroup`
125
+
126
+
##### `token_type` is `user-service-account`
127
+
128
+
Format of the path is `{username}` example `service_account_65c74d39b4f71fc3fdc72330fce28c28`.
129
+
130
+
##### `token_type` is `group-service-account`
131
+
132
+
Format of the path is `{groupId}/{serviceAccountName}` example `265/service_account_65c74d39b4f71fc3fdc72330fce28c28`.
133
+
134
+
##### `token_type` is `project-deploy`
135
+
136
+
Format of the path is the full path of the project for example `group/project` or `group/subgroup/project`
137
+
138
+
##### `token_type` is `group-deploy`
139
+
140
+
Format of the path is the full path of the project for example `group` or `group/subgroup`
141
+
142
+
##### `token_type` is `pipeline-project-trigger`
143
+
144
+
Format of the path is the full path of the project for example `group/project` or `group/subgroup/project`
113
145
114
146
#### name
115
147
@@ -154,17 +186,20 @@ Depending on `gitlab_revokes_token` the TTL will change.
154
186
155
187
#### access_level
156
188
157
-
It's not required if `token_type` is set to `personal`.
189
+
It's not required if `token_type` is set to `personal`, `pipeline-project-trigger`, `project-deploy`, `group-deploy`.
158
190
159
191
For a list of available roles check https://docs.gitlab.com/ee/user/permissions.html
160
192
161
193
#### scopes
162
194
195
+
It's not required if `token_type` is set to `pipeline-project-trigger`.
196
+
163
197
Depending on the type of token you have different scopes:
0 commit comments