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
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,10 +106,20 @@ anti requester generate-assets -D ./path/to/your/test/directory
106
106
Once you modified them you can try to run them locally with the `anti requester test-run` command.
107
107
108
108
```bash
109
-
anti agent test-run -D ./path/to/your/test/directory
109
+
anti agent test-run -D ./path/to/your/test/directory (TBD)
110
110
```
111
111
112
-
Then commit and push the changes to your repository.
112
+
Then commit and push the changes to your repository so you will have a commit hash to use when requesting the test-run.
113
+
114
+
In general your test assets directory should contain at least a `docker-compose.yaml` file with all its images published on a public registry (like DockerHub or GHCR).
115
+
Any other asset in the test assets directory can be made available to any of your containers via a bind mount from the current working directory on the host.
116
+
117
+
i.e. if you have an asset file `myconfig.json` in the test directory, it will be available to a container if you add a volume mount like this to your `docker-compose.yaml` file:
0 commit comments