terraform-starter VS terragrunt-atlantis-config

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

I've also made the switch from managing a few thousand Terraform modules to handling most app-code things in Pulumi and have run into some of these limitations.

With Terraform + Terragrunt + Atlantis, we created https://github.com/transcend-io/terragrunt-atlantis-config and had an extremely robust and easy to use flow for updating all infra code.

We've since moved to an approach where more of our infra/security things are managed in Terraform (like Guardduty, SSO, Github repo settings, etc.) maintained by more devops folks, and our app code is mostly in Pulumi (lambdas, Fargate, CloudFront/CloudFlare CDNs, etc.). To accomplish this without something like Atlantis, we moved the app code infra deployments from being deployed continuously pre-merge via Atlantis to being deployed via `pulumi up` calls in our normal CI flows, so like right next to where we build the docker images and restart ECS services, as an example.

Overall I actually really love this flow. It is so, so much easier to create multi-regional infra in Pulumi with a quick for loop, and it's also much easier to do things like run esbuild over our code in typescript, and then bundle the output of that call and send it up to a Lambda function all from pulumi/typescript without needing separate build steps or to do things like using terragrunt pre-hooks or Docker build steps inside terraform provisioners, which I always found slow and clunky.

I would agree that Pulumi's plans are a disappointment though, exactly as you said.

Overall I've been happy with the change, and we've seen some improvements I think in the velocity that developers can launch services that meet our requirements.

I recommend atlantis with terragrunt-atlantis-config.

I know this is a bit too specific, it is about the ` terragrunt-atlantis-config tool, but in case anyone has come across this issue any help would be highly appreciated.

I've managed to make it work but it was really hard for me to set it up correctly. My biggest issue was that I didn't want every Terragrunt module to be run when I've opened a PR. Have a look at this project which helped me to run only the modules witch changes in every PR. Note that, I last used Atlantis a year ago so I don't know if they recently made changes for better Terragrunt support.

The most recent release of Atlantis includes a new feature that allows you to register a hook before atlantis reads its atlantis.yaml config. You can now dynamically build your atlantis.yaml file in the atlantis itself. I think using something like terragrunt-atlantis-config can make working with terragrunt easier.