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 file is always treated as part of the artifact: its own entries cannot exclude it, so the exclusion list cannot be changed without changing the fingerprint.
Paths the list already matches stay excluded whatever is later added there, so keep its entries as narrow as possible.
Excluding the file with --exclude keeps it out of the fingerprint but still applies the paths it lists, which lets a writable directory change the list again.
To drop the file from the fingerprint safely, move its entries to --exclude and delete it.
Flags
Flags inherited from parent commands
Examples Use Cases
These examples all assume that the flags--api-token, --org, --host, (and --flow, --trail when required), are set/provided.