diff --git a/website/content/posts/a-taste-of-policies.md b/website/content/posts/a-taste-of-policies.md index ec7a52ac..8d69bb3b 100644 --- a/website/content/posts/a-taste-of-policies.md +++ b/website/content/posts/a-taste-of-policies.md @@ -11,6 +11,8 @@ policies. +{{< conforma-name-preamble >}} + Throughtout this post, we will use a container image from one of the author's side projects. This image was [built](https://github.com/lcarva/festoji/blob/848edc452ccbc6d42ec56c2807eef2f49e754c5e/.github/workflows/package.yaml) diff --git a/website/content/posts/evaluating-custom-predicates.md b/website/content/posts/evaluating-custom-predicates.md index d0df2d68..66eb1a1c 100644 --- a/website/content/posts/evaluating-custom-predicates.md +++ b/website/content/posts/evaluating-custom-predicates.md @@ -13,6 +13,8 @@ assert the contents of *any* attestation format, even completely made up ones. +{{< conforma-name-preamble >}} + Before getting started, let's make sure we have an image that is already signed and has a SLSA Provenance attestation. We will also need access to the signing key used. The [Hitchhiker’s Guide](https://enterprisecontract.dev/docs/user-guide/hitchhikers-guide.html) walks through the diff --git a/website/content/posts/gating-image-promotion-on-gitlab.md b/website/content/posts/gating-image-promotion-on-gitlab.md index 725acf45..c90d4e3b 100644 --- a/website/content/posts/gating-image-promotion-on-gitlab.md +++ b/website/content/posts/gating-image-promotion-on-gitlab.md @@ -10,6 +10,8 @@ achieve this in a [GitLab] pipeline. +{{< conforma-name-preamble >}} + > See the [appendix](#appendix) section for the full example. Consider a simple [.gitlab-ci.yaml] file: diff --git a/website/content/posts/introducing-action-validate-image.md b/website/content/posts/introducing-action-validate-image.md index f9c38896..ccdf0470 100644 --- a/website/content/posts/introducing-action-validate-image.md +++ b/website/content/posts/introducing-action-validate-image.md @@ -11,6 +11,8 @@ processes or any other automated workflow in GitHub. +{{< conforma-name-preamble >}} + ## What is EC Validate Action? **EC Validate** is a GitHub Action that brings validation capabilities of the Enterprise Contract CLI directly into your GitHub Workflow. Designed to integrate seamlessly into your build pipeline, this action offers both compliance assessments and integrity checks for your container images. It ensures that your images meet both organizational and industry standards before deployment or environment promotion. diff --git a/website/content/posts/introducing-the-enterprise-contract.md b/website/content/posts/introducing-the-enterprise-contract.md index be9433d3..b0f441fc 100644 --- a/website/content/posts/introducing-the-enterprise-contract.md +++ b/website/content/posts/introducing-the-enterprise-contract.md @@ -10,6 +10,8 @@ built on those technologies. +{{< conforma-name-preamble >}} + ## Before starting… Let’s say you have an image, `quay.io/lucarval/demo:ec`, and you want to verify this image was signed diff --git a/website/layouts/shortcodes/conforma-name-preamble.html b/website/layouts/shortcodes/conforma-name-preamble.html new file mode 100644 index 00000000..56f00235 --- /dev/null +++ b/website/layouts/shortcodes/conforma-name-preamble.html @@ -0,0 +1,24 @@ + +
+ + + + + + + +
+ + + This blog post refers to Conforma by its original name, "Enterprise Contract". + But don't worry! The only thing we've changed is the name. The examples described + here should work exactly the same. +
+