Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
…se, and dark controls paragraph
|
Was this released yet? I cannot see this in Kosli 🤔 |
No this is a proposed feature. We are making this documentation ahead of development to facilitate discussions and get early feedback before we build it. |
|
Okay, I assume we're not releasing this to docs yet then? I think it might confuse our customers. |
…ple to use kosli evaluate
|
Perhaps we can make this a "draft" PR?, just to prevent it being merged :) |
|
|
||
| ### Deployments | ||
|
|
||
| The Deployments tab shows where artifacts with decisions against this control have been deployed, with compliant/non-compliant status per deployment, filterable by repository, flow, and environment. |
There was a problem hiding this comment.
How do we get the correct list of environments that this Control should apply to for deployments and Coverage views?
Potential options
- Default filter to environments that have had a decision recorded for this Control (ever, in time range?).
- Easy first attempt
- Need to ensure this gives a realistic coverage (decision recorded ever would be consistent, but how do you remove from filter)
-
Default filter to environments that have Control mentioned in environment policy.
-
Add explicit mappings on Controls to environments they apply to that Customers should maintain.
| | `--attachments` | Optional evidence file(s) to attach (e.g. an evaluation report, a REGO policy output). | | ||
| | `--user-data` | Optional path to a JSON file containing additional structured data to attach to the attestation. | | ||
|
|
||
| The decision attestation goes on a trail, like any other attestation. It affects trail compliance: a `--compliant false` decision makes the trail non-compliant. There are no restrictions on which flow or trail a decision can be recorded on — place it wherever makes sense in your process, typically at the point where the decision is actually being made (e.g. during a release preparation or promotion step). |
There was a problem hiding this comment.
Should there be any distinctions around how a decision attestation appears on a trail.
Can it be given a named slot?
…tutorial Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…onment Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…policy/v1 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…identifier Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Summary
tutorials/working_with_controls.mdx— a tutorial covering how to define controls in Kosli, record decisions against them, reference them in environment policies, and view compliance across deployments.config/navigation.jsonto include the new page under a new "Controls" group in the Tutorials section.Closes kosli-dev/server#5355