Synopsis
You can report a directory or file artifact. For reporting multiple artifacts in one go, use “kosli snapshot paths”. You can exclude certain paths or patterns from the artifact fingerprint using
--exclude.
The supported glob pattern syntax is documented here: https://pkg.go.dev/path/filepath#Match ,
plus the ability to use recursive globs ”**”
To specify paths in a directory artifact that should always be excluded from the SHA256 calculation, you can add a .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.
report one artifact running in a specific path in a filesystem
report one artifact running in a specific path in a filesystem
report one artifact running in a specific path in a filesystem AND exclude certain path patterns
report one artifact running in a specific path in a filesystem AND exclude certain path patterns