Skip to content

docs: fix assert artifact scopes - --flow is not mutually exclusive #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dangrondahl merged 1 commit into from
Apr 9, 2026
Merged

docs: fix assert artifact scopes - --flow is not mutually exclusive #133

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions getting_started/enforce_policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,14 +15,17 @@ All methods use the same assertion: checking an artifact's fingerprint against a

## Assertion scopes

`kosli assert artifact` (and its API equivalent) supports four mutually exclusive scopes:
`kosli assert artifact` (and its API equivalent) supports three assertion modes:

| Scope | CLI flag | When to use |
|-------|----------|-------------|
| Mode | CLI flag | When to use |
|------|----------|-------------|
| Environment | `--environment` | Check all policies attached to the target environment. The most common choice for deployment gates. |
| Specific policies | `--policy` | Check one or more named policies, regardless of environment attachment. Useful for promotion gates between stages. |
| Flow template | `--flow` | Check the artifact against a flow's template requirements. |
| All flows | _(no scope flag)_ | Check against the templates of every flow the artifact appears in. |
| Flow templates | _(no scope flag)_ | Check against the template files of the flows the artifact appears in. |

`--environment` and `--policy` are mutually exclusive.

`--flow` can be combined with any mode to narrow the lookup to a specific flow. Without `--flow`, all flows containing the artifact (by fingerprint) are considered.

See [`kosli assert artifact`](/client_reference/kosli_assert_artifact) for the full flag reference.

Expand Down