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: cli/docs/requester-role.md
+28-12Lines changed: 28 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,28 +104,44 @@ Then commit and push the changes to your repository.
104
104
105
105
### Requesting a test-run
106
106
107
+
#### SSH key setup
107
108
Before proceding be careful to set the necessary signing assets in your environment variables.
108
-
```bash
109
-
Which key selector to use from the SSH file
110
-
env: ANTI_SSH_KEY_SELECTOR STRING
111
109
112
-
Path to the SSH private key file
113
-
env: ANTI_SSH_FILE FILEPATH
110
+
- `anti` will use the SSH private key to sign the request
111
+
- The private key has to be an ed25519 key.
112
+
- The public key corresponding to the private key has to be registered in your github account [see above](#registering-a-user-public-key).
113
+
114
+
Multiple keys file are supported, in this case you have to specify which key to use with the `ANTI_SSH_KEY_SELECTOR` environment variable or the `--ssh-key-selector` option.
115
+
In case you don't know the selector, you can inspect the keys in your file with
116
+
117
+
```bash
118
+
anti ssh-selectors --ssh-file PATH_TO_YOUR_SSH_FILE --ask-ssh-passphrase
114
119
```
115
120
116
-
As with the wallet passphrase you can set the password in the environment variable
121
+
If multiple keys are present in the file and you don't specify a selector, the first key in the file will be used.
122
+
123
+
To link to your private key file, set the `ANTI_SSH_FILE` environment variable to point to it.
124
+
125
+
126
+
As with the wallet passphrase you can set the password in the environment variable (not recommended)
117
127
118
128
```bash
119
-
read -s -p "Enter password to decrypt the SSH private key: "ANTI_INTERACTIVE_SECRETS
120
-
export ANTI_INTERACTIVE_SECRETS
129
+
read -s -p "Enter password to decrypt the SSH private key: "ANTI_SSH_PASSWORD
130
+
exportANTI_SSH_PASSWORD
121
131
```
122
132
123
-
Or better paste it from a password manager each time you need it using the 'ask-password' option
133
+
Or better paste it from a password manager each time you need it using the `--ask-ssh-password` option
124
134
125
-
Or set the `ANTI_INTERACTIVE_SECRETS` environment variable to any value.
135
+
Or set the `ANTI_INTERACTIVE_SECRETS` environment variable to any value to imply the `--ask-ssh-password` option
136
+
137
+
```bash
138
+
export ANTI_INTERACTIVE_SECRETS=1
139
+
```
126
140
127
141
> The file at ANTI_SSH_FILE path has to be the encrypted ssh private key matching the user registration [see above](#registering-a-user-public-key).
128
142
143
+
#### Requesting the test-run
144
+
129
145
To request a test-run, you can use the `anti requester create-test` command.
130
146
131
147
```bash
@@ -135,7 +151,7 @@ anti requester create-test --platform github --username alice --repository youro
135
151
136
152
You can request multiple test-runs for the same commit but you have to specify a different `--try` number for each request.
137
153
138
-
### Checking the test-run status
154
+
#### Checking the test-run status
139
155
140
156
You can check the status of your test-run requests with the `anti facts test-runs` command.
141
157
@@ -146,5 +162,5 @@ anti facts test-runs -i <your_test_run_id>
146
162
You can find all running test-runs for a user with
0 commit comments