terragrunt-atlantis-config
org-formation-cli
terragrunt-atlantis-config | org-formation-cli | |
---|---|---|
8 | 27 | |
565 | 1,341 | |
2.8% | 0.5% | |
7.8 | 6.2 | |
4 days ago | 25 days ago | |
HCL | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terragrunt-atlantis-config
-
Pulumi Insights – AI generated IaC programs
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.
-
Any examples of Terragrunt used in Github Actions?
I recommend atlantis with terragrunt-atlantis-config.
- Atlantis with Terragrunt
-
Error on terragrunt-atlantis-config on project generation
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.
-
Do you use Atlantis for Terraform dev collaboration?
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.
- Automating AWS Organizations & Best practices around using CI/CD for IaaC deployments
- Enhancing the Terraform Experience: Why we use Terragrunt
-
Terragrunt — Becoming one with its internal behaviors
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.
org-formation-cli
- Show HN: An Infrastructure as Code (IaC) Tool for AWS Organizations
-
No, you don’t need to test every line of your CDK application
And these guardrails are usually owned by platform teams. One downside to doing all these with AWS Organizations is that it involves a lot of clickops… This is where I would turn to org-formation, an open-source tool that gives you infrastructure-as-code for AWS Organizations. It’s a really powerful tool and I strongly recommend that you check it out if you haven’t already.
-
AWS simple multi account setup
If you don’t like control tower, try org formation. https://github.com/org-formation/org-formation-cli
- AWS Organization Formation
-
How to structure the common setup for multiple account in an organization
I found myself bootstrapping a new AWS Organization. I am using org-formation to define the basic account structure, an OIDC IdP for Github Actions and the essential roles for Terraform to do its job.
-
Is a well-designed security group and instance profile enough to limit tenants to their VM in a single VPC
an AWS account is free, so if you're planning basically reselling AWS, an account per tenant is a nobrainer. There are a few ways to create loads of accounts, org-formation is my favorite
-
EXPERIENCE WITH AWS CONTROL TOWER
We use https://github.com/org-formation/org-formation-cli for most of our work, though just vanilla Terraform can work reasonably well for most of the things.
-
CloudFormation deploying cross-account resources
By the way, if you like the "deploy this stack to multiple accounts"-feature of Stacksets, you're going to lovveee org-formation.
-
Leveraging CodePipeline to deploy Terraform
This led me to two problems. The first was the perennial issue I've had with Terraform from day one: "How do I manage state?". The second issue was how do I leverage some form of CI/CD tooling to allow me to leverage one of Terraform's biggest strengths - the terraform plan capability. Since Fooli is an AWS product, I figured that I should be able to use AWS native tools for this. I've used CodePipeline in the past to preview change-sets with aws-org-formation, so I thought it would be easy to find a well-worn pattern from AWS on doing it.
-
Top 12 Serverless Announcements from re:Invent 2022
You can now manage your AWS Organization through CloudFormation, including creating accounts, organizational units, and policies. It's one of those things you are surprised were not already possible. However, I will stick to the OrgFormation for my own accounts, as it offers additional features like deploying stacks and performing custom logic across the organization.
What are some alternatives?
terragrunt-infrastructure-live-example - A repo used to show examples file/folder structures you can use with Terragrunt and Terraform
superwerker - superwerker can help you get started with the AWS Cloud quickly without investing in consultants or devoting time to extensive research. superwerker is a free, open-source solution that lets you quickly set up an AWS Cloud environment following best practices for security and efficiency so you can focus on your core business.
terraform-aws-ecs-atlantis - Terraform module for deploying Atlantis as an ECS Task
serverless - This is intended to be a repo containing all of the official AWS Serverless architecture patterns built with CDK for developers to use. All patterns come in Typescript and Python with the exported CloudFormation also included.
terraform-aws-atlantis - Terraform module to deploy Atlantis on AWS Fargate 🇺🇦
cloudformation-aws-landing-zone - AWS Landing Zone Template v2.4.6(Latest)
modules.tf-demo - Real modules.tf demo (updated May 2021)
mutato - Repo formerly known as mu-cdk. A.K.A Mu2. Pronounced: mew-tah-toe
terraform-starter - Starter repository to play with Spacelift
aws-control-tower-customizations - The Customizations for AWS Control Tower solution combines AWS Control Tower and other highly-available, trusted AWS services to help customers more quickly set up a secure, multi-account AWS environment using AWS best practices.
terraform-aws-eks - Terraform module to create AWS Elastic Kubernetes (EKS) resources 🇺🇦
aws-export-credentials - Get AWS credentials from a profile to inject into other programs