Problem
The scoping table on /getting_started/environments shows the S3 (buckets) row with no support for any scoping option (all resources, by name, by regex, exclude by name, exclude by regex). This contradicts the kosli snapshot s3 CLI reference, which documents --include/--exclude (literal prefix) and --include-regex/--exclude-regex (Go regex against the full object key).
Expected Behavior
The table reflects S3 filtering, or the page clarifies the distinction: S3 filtering selects which objects contribute to the fingerprint, but the result is always reported as a single artifact.
Current Behavior
Readers evaluating whether S3 content can be scoped conclude, incorrectly, that no filtering exists.
Suggested Approach
Update the S3 row to reflect include/exclude and include/exclude-regex, and add a note that filtered content still reports as one artifact. Cross-link the kosli snapshot s3 reference.
Problem
The scoping table on /getting_started/environments shows the S3 (buckets) row with no support for any scoping option (all resources, by name, by regex, exclude by name, exclude by regex). This contradicts the
kosli snapshot s3CLI reference, which documents--include/--exclude(literal prefix) and--include-regex/--exclude-regex(Go regex against the full object key).Expected Behavior
The table reflects S3 filtering, or the page clarifies the distinction: S3 filtering selects which objects contribute to the fingerprint, but the result is always reported as a single artifact.
Current Behavior
Readers evaluating whether S3 content can be scoped conclude, incorrectly, that no filtering exists.
Suggested Approach
Update the S3 row to reflect include/exclude and include/exclude-regex, and add a note that filtered content still reports as one artifact. Cross-link the
kosli snapshot s3reference.