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
- venom: load .so plugins only from --lib-dir (no auto-load from workdir);
validate plugin name against [A-Za-z0-9_-]
- http: reject absolute paths for tls_root_ca/tls_client_cert/tls_client_key;
detect inline PEM via "-----BEGIN" marker; fail explicitly when file is
missing
- exec: fix Windows .ps1 rename (create temp script with final name);
create temp script atomically with O_EXCL and 0o700; document
stdout/stderr synchronization
- ssh: add configurable `timeout` field (default 30s); restrict privatekey
absolute paths to $HOME, resolve relative paths under workdir
- html report: sanitize markdown rendering with DOMPurify
BREAKING CHANGE: .so plugins now require --lib-dir; HTTP TLS file paths
must be relative to workdir; SSH privatekey absolute paths must be under
$HOME.
Signed-off-by: Yvonnick Esnault <yvonnick.esnault@ovhcloud.com>
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -419,6 +419,8 @@ Notice the variable `alljson`. All variables declared in output are automaticall
419
419
Venom will load user-defined executors from the directory `lib/` relative to the testsuite path. You can add executor source paths using the flag `--lib-dir`.
420
420
Note that all folders listed with `--lib-dir` will be scanned recursively to find `.yml` files as user executors.
421
421
422
+
Compiled Go plugins (`.so`) are **only** loaded from `--lib-dir`; they are no longer auto-discovered from `<workdir>/lib/`. The plugin name (the YAML `type:` field) must match `[A-Za-z0-9_-]+`.
423
+
422
424
The user defined executors work with templating, you can check the templating result in `venom.log`. In this file, if you see an error such as `error converting YAML to JSON: yaml: line 14: found unexpected end of stream`, you probably need to adjust indentation with the templating function `indent`.
Copy file name to clipboardExpand all lines: executors/http/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,9 +23,9 @@ In your yaml file, you can use:
23
23
- no_follow_redirect (optional): indicates that you don't want to follow Location if server returns a Redirect (301/302/...)
24
24
- skip_body: skip the body and bodyjson result
25
25
- skip_headers: skip the headers result
26
-
- tls_client_cert (optional): a chain of certificates to identify the caller, first certificate in the chain is considered as the leaf, followed by intermediates. Setting it enables mutual TLS authentication. Set the PEM content or the path to the PEM file.
27
-
- tls_client_key (optional): private key corresponding to the certificate. Set the PEM content or the path to the PEM file.
28
-
- tls_root_ca (optional): defines additional root CAs to perform the call. Can contain multiple CAs concatenated together. Set the PEM content or the path to the PEM file.
26
+
- tls_client_cert (optional): a chain of certificates to identify the caller, first certificate in the chain is considered as the leaf, followed by intermediates. Setting it enables mutual TLS authentication. Provide either inline PEM content (must contain "-----BEGIN") or a path relative to the testsuite workdir. Absolute paths are rejected.
27
+
- tls_client_key (optional): private key corresponding to the certificate. Provide either inline PEM content or a path relative to the testsuite workdir.
28
+
- tls_root_ca (optional): additional root CAs used for the call. Can contain multiple CAs concatenated together. Provide either inline PEM content or a path relative to the testsuite workdir.
0 commit comments