Documentation Index
Fetch the complete documentation index at: https://kosli-reference-docs-v2-17-6.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Synopsis
You can report directory or file artifacts in one or more server paths. When fingerprinting a ‘dir’ artifact, you can exclude certain paths from fingerprint calculation using the
--exclude flag.
Excluded paths are relative to the DIR-PATH and can be literal paths or glob patterns.
With a directory structure like this foo/bar/zam/file.txt if you are calculating the fingerprint of foo/bar you need to
exclude zam/file.txt which is relative to the DIR-PATH.
The supported glob pattern syntax is what is documented here: https://pkg.go.dev/path/filepath#Match ,
plus the ability to use recursive globs ”**”
If the directory structure contains a symbolic link to a file (for example, a link ‘from/this/file’ and a target of ‘to/another/file’) then:
- the name of the link (‘from/this/file’) is included in the fingerprint.
- the name of the link (‘from/this/file’) is subject to
.kosli_ignoreentries. - the name of the target (‘to/another/file’) is not included in the fingerprint.
- the content of target is included in the fingerprint, even if the target is outside the root directory being fingerprinted.
- the name of the link (‘from/this/dir’) is included in the fingerprint.
- the name of the link (‘from/this/dir’) is subject to
.kosli_ignoreentries. - the name of the target (‘to/another/dir’) is included in the fingerprint, even if the target is outside the root directory being fingerprinted.
- the name of the target (‘to/another/dir’) is not subject to
.kosli_ignoreentries. - the content of the target is not included in the fingerprint.
.kosli_ignore file to the root of the artifact.
Each line should specify a relative path or path glob to be ignored. You can include comments in this file, using #.
The .kosli_ignore will be treated as part of the artifact like any other file, unless it is explicitly ignored itself.
Flags
| Flag | Description |
|---|---|
| -D, —dry-run | [optional] Run in dry-run mode. When enabled, no data is sent to Kosli and the CLI exits with 0 exit code regardless of any errors. |
| -x, —exclude strings | [optional] The comma separated list of directories and files to exclude from fingerprinting. Can take glob patterns. |
| -h, —help | help for server |
| -p, —paths strings | The comma separated list of absolute or relative paths of artifact directories or files. Can take glob patterns, but be aware that each matching path will be reported as an artifact. |
Flags inherited from parent commands
| Flag | Description |
|---|---|
| -a, —api-token string | The Kosli API token. |
| -c, —config-file string | [optional] The Kosli config file path. (default “kosli”) |
| —debug | [optional] Print debug logs to stdout. A boolean flag docs (default false) |
| -H, —host string | [defaulted] The Kosli endpoint. (default “https://app.kosli.com”) |
| —http-proxy http://proxy-server-ip:proxy-port | [optional] The HTTP proxy URL including protocol and port number. e.g. http://proxy-server-ip:proxy-port |
| -r, —max-api-retries int | [defaulted] How many times should API calls be retried when the API host is not reachable. (default 3) |
| —org string | The Kosli organization. |
Examples Use Cases
These examples all assume that the flags--api-token, --org, --host, (and --flow, --trail when required), are set/provided.