Skip to content

Commit d071162

Browse files
committed
[cli] docs: document generate assets
1 parent e5ac91c commit d071162

File tree

1 file changed

+12
-2
lines changed

1 file changed

+12
-2
lines changed

cli/docs/requester-role.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,10 +106,20 @@ anti requester generate-assets -D ./path/to/your/test/directory
106106
Once you modified them you can try to run them locally with the `anti requester test-run` command.
107107

108108
```bash
109-
anti agent test-run -D ./path/to/your/test/directory
109+
anti agent test-run -D ./path/to/your/test/directory (TBD)
110110
```
111111

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:
118+
119+
```yaml
120+
volumes:
121+
- ./myconfig.json:/etc/myapp/config.json:ro
122+
```
113123
114124
### Requesting a test-run
115125

0 commit comments

Comments
 (0)