Skip to content

Commit 9ee653b

Browse files
committed
Add information about expired tokens
Show how to update expired Github tokens. Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
1 parent d9c1fc1 commit 9ee653b

1 file changed

Lines changed: 16 additions & 0 deletions

File tree

github/azure-self-hosted-runners/README.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -121,3 +121,19 @@ $ az container logs -g garm -n garm-kg1ocu --container-name garm --follow
121121
}
122122
127.0.0.1 - - [02/Jun/2023:13:01:21 +0000] "GET /api/v1/metadata/runner-registration-token/ HTTP/1.1" 200 29 "" "curl/7.81.0"
123123
```
124+
125+
## Updating expired Github tokens
126+
127+
The Github tokens should be updated in the Garm installation from time-to-time because they expire. You will need to re-generate the expired token(s) first.
128+
129+
Then you will need to update its value on the Key Vault. For example, suppose the new token is "github_pat_xxxxxxxx", to update the "garm" secret in the "garm-github-tokens" vault:
130+
131+
```
132+
$ az keyvault secret set --value github_pat_xxxxxxxx --name garm --vault-name garm-github-tokens
133+
```
134+
135+
Finally you will need to re-deploy Garm:
136+
137+
```bash
138+
$ terraform apply
139+
```

0 commit comments

Comments
 (0)