terraform-starter VS OPA (Open Policy Agent)

We obviously don't have a project for your exact use case, but we have an open-source example repo that shows a fairly advanced scenario of using the Terraform Spacelift Provider https://github.com/spacelift-io/demo-preview-environments-manager, a simple quickstart of using it https://github.com/spacelift-io/terraform-starter and you can also see the CloudPosse Atmos project, for a very advanced scenario which generates lot's of Stacks based on your component specifications https://github.com/cloudposse/atmos.

Use our starter repository to play with Spacelift (guide)

If you're looking for TFC alternatives where you can manage your own state, https://spacelift.io is another option. We've got a tutorial walking you through creating an account and using Spacelift here if you wanna give it a try: https://github.com/spacelift-io/terraform-starter

Spacelift goes a few steps further though and puts policy-as-code in the center of its value proposition and builds a consistent, robust policy framework. Apart from providing a comprehensive automated change review and ensuring compliance of your Terraform changes, Spacelift uses the same approach to allow you to declare rules around account and project access, handling push notifications, starting runs and triggering tasks, and creating relationships between projects. It also provides the Policy Workbench, which lets you view past executions of your policy – including the inputs and decisions that have been made – and lets you interactively edit your policy, while simulating its execution on these previous inputs. You can use our starter repo to quickly provision a bunch of policies and get a feel for how you can work with them in Spacelift.

PS: If you want to quickly check out Spacelift (literally 15 minutes of your time) come and take a look at our Starter Repository!

Feel free to [schedule a chat/demo with us](https://spacelift.io/schedule-demo.html) or tu play with our starter repo to [learn more](https://github.com/spacelift-io/terraform-starter).

Hi HN!

We are the team behind Spacelift (https://spacelift.io/). Spacelift is the CI/CD for infrastructure-as-code, be it Terraform, Pulumi, CloudFormation or Ansible (coming soon), and policy as code. It enables collaboration, automates manual work and compliance, and lets teams customize and automate their workflows.

Here’s what you can do with Spacelift

- Build sophisticated Git-based workflows

- Use Open Policy Agent to declare rules around your infrastructure, access control, state changes, and more

- Author and maintain reusable modules for your organization; we even have a full CI solution for modules to make sure they’re healthy

- Declare who can log in (and under what circumstances) and what their level of access to each of the managed projects should be (SAML 2.0 SSO out of the box!) using login and access policies respectively

- Use Spacelift’s trigger policies to create arbitrary workflows and dependencies spanning multiple infrastructure-as-code stacks

- Manage stacks, contexts, modules, and policies in a declarative way using Terraform or Pulumi

Before Spacelift, we built bespoke solutions (e.g., Geopoiesis, https://www.reddit.com/r/Terraform/comments/fu6pj1/geopoiesisio_anyone_knows_something_about_it/), currently used by two of the largest European scaleups.

In the past few months, we’ve been onboarding our first customers and making sure everything works as expected. You can check out our starter repo at https://github.com/spacelift-io/terraform-starter. It's an easy way to learn all of Spacelift’s capabilities in 15 minutes without tapping into your own cloud resources. We’d love your thoughts on our approach and anything that has worked or hasn’t worked for you.

P.S. We are hiring https://spacelift.io/careers

How can we handle this? Are there any mechanisms to prevent or at least to some extent safeguard this kind of issues without falling back to a manual workflow? There is. One huge advantage of sticking to (de-facto) standards like Terraform is that first we are probably not the first ones to come up with this question and second there is a huge ecosystem around Terraform that might help us with such challenges. And for this specific scenario the solution is the Open Policy Agent. Let us take a closer look how the solution could look like.

A popular Policy-as-Code tool for Terraform is OPA, everyone's favorite versatile open-source policy engine that enforces security and compliance policies across your cloud-native stack, making it easier to manage and maintain consistent policy enforcement in complex, multi-service environments.

Harness Policy As Code uses Open Policy Agent (OPA) as the central service to store and enforce policies for the different entities and processes across the Harness platform. In this section, you will define a policy that will deny a pipeline execution if there is no approval step defined in a deployment stage.

OPA: While OPA is an open-source, general-purpose policy engine capable of enforcing unified and context-aware policies throughout the stack, it can also accept and output data in formats such as JSON, effectively functioning as a tool for generating or modifying configurations. Although it does not provide out-of-the-box schema definition support, it allows the integration of JsonSchema definitions.

In essence, container image signing involves adding a digital stamp to an image, affirming its authenticity. This digital assurance guarantees that the image is unchanged from creation to deployment. In this blog, I'll explain how to sign container images for Kubernetes using Cosign and the Open Policy Agent. I will also share a tutorial that demonstrates these concepts.

In this post we will explores two powerful solutions for addressing this issue: the Open Policy Language (OPA) and Google’s Zanzibar.

Rego is a declarative query language from the makers of the Open Policy Agent (OPA) framework. The Cloud Native Computing Foundation (CNCF) accepted OPA as an incubation-level hosted project in April 2019, and OPA graduated from incubating status in 2021.

Now there are more subdivided practice: * Policy as Code: Sentinel, OPA * Database as Code: bytebase * AppConfiguration as Code: KusionStack, Acorn * ...... (Welcome to add more)