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
Copy file name to clipboardExpand all lines: docs/access-token.md
+30-2Lines changed: 30 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,9 @@
1
1
# Access Token
2
2
3
+
## Overview
3
4
If you want to automate tasks with the Argo Server API or CLI, you will need an access token.
4
5
6
+
## Pre-requisites
5
7
Firstly, create a role with minimal permissions. This example role for jenkins only permission to update and list workflows:
6
8
7
9
```sh
@@ -14,15 +16,19 @@ Create a service account for your service:
14
16
kubectl create sa jenkins
15
17
```
16
18
17
-
!! TIP
18
-
Create a unique service account for each client: (a) you'll be able to correctly secure your workflows and (b) [revoke the token](#token-revocation) without impacting other clients.
19
+
### Tip for Tokens Creation
20
+
Create a unique service account for each client:
21
+
22
+
- (a) you'll be able to correctly secure your workflows
23
+
- (b) [revoke the token](#token-revocation) without impacting other clients.
19
24
20
25
Bind the service account to the role (in this case in the `argo` namespace):
0 commit comments