v0.21.1

After a previous tick release focused on performance, it's time for a new release, but this time packing some big features! 🚀

AWS S3 CAS backend support

We welcome Amazon S3 blob storage as a new addition to the CAS backend family, joining OCI registry and Azure Blob Storage. Now, you can configure an S3 bucket as a destination for all your SDLC pieces of evidence (SBOMS, artifacts, test results, VEX files) and attestations.

You can learn how to configure it in our documentation, but in a nutshell...

 $ chainloop cas-backend add aws-s3 \
    --access-key-id [accessKeyID] \
    --secret-access-key [secretAccessKey] \
    --region [region] \
    --bucket [bucketName]

The result is having all the artifacts stored in your s3 bucket following a content addressable convention.

With tamper-resistant properties and additional information for easy retrieval.

Azure KeyVault credentials backend

This release also adds support for Azure KeyVault. This means that when you deploy Chainloop in Azure, you can now fully leverage Azure-managed services by not only using CloudSQL (for DB) and Azure Blob Storage (for content addressable storage (CAS)) but also Azure KeyVault for credentials handling.

This makes this deployment topology on par with what we already have in Google Cloud (via GCP secret manager) and Amazon Web Services (with AWS secret manager). Congratulations, Azure users! 🎉

You can find the full release attestation here

What's Changed

• Bump Helm Chart Version => v0.20.0 by @github-actions in #384
• fix: Azure Pipeline Run URI incorrect value by @danlishka in #386
• chore(deps): Bump golang.org/x/net from 0.15.0 to 0.17.0 by @dependabot in #387
• feat: Azure KeyVault support by @migmartri in #388
• feat(deployment): Azure KeyVault support by @migmartri in #389
• feat(CAS): AWS S3 blob storage support by @migmartri in #390
• Bump Helm Chart Version => v0.21.0 by @github-actions in #391
• fix(azure): existing file regression by @migmartri in #392

Full Changelog: v0.20.0...v0.21.1