From 00b0546c9f87fe93be9339c27493ad40045c0afb Mon Sep 17 00:00:00 2001 From: Daniel Liszka Date: Wed, 31 May 2023 10:05:50 +0200 Subject: [PATCH] feat: Add support for JUnit XML material type (chainloop-dev/chainloop#120) Signed-off-by: Daniel Liszka --- docs/reference/operator/contract.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/operator/contract.mdx b/docs/reference/operator/contract.mdx index e9b8c39..d86a741 100644 --- a/docs/reference/operator/contract.mdx +++ b/docs/reference/operator/contract.mdx @@ -48,7 +48,7 @@ A full example of a Workflow Contract looks like | Name | Required | Default | Description | | ---------- | -------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | yes | | unique identifier of the artifact | -| `type` | yes | | | +| `type` | yes | | | | `output` | no | `false` | If set to `true` the artifact will get injected in the `subject` section of the [in-toto statement](https://github.com/slsa-framework/slsa/blob/main/docs/attestation-model.md#overview). | | `optional` | no | `false` | if set to `true`, providing this artifact during attestation will be optional. This is **useful for soft rollouts of new requirements** |