sandbox
sandbox copied to clipboard
[Sandbox] Atlantis
Application contact emails
[email protected] [email protected]
Project Summary
Terraform Pull Request Automation
Project Description
Atlantis is PR automation application that allows users to create PRs against a repository to run terraform via command comments like atlantis plan/apply/import/unlock
.
It allows users to interact with terraform commands within the PR and get the output of those commands in the form of PR comments.
Users can define project structures, generate policies, autogenerate projects, require review requirements etc.
Atlantis supports multiples VCSs Github, Gitlab, BitBucket, Azure Pipelines
Org repo URL (provide if all repos under the org are in scope of the application)
https://github.com/runatlantis
Project repo URL in scope of application
https://github.com/runatlantis/atlantis
Additional repos in scope of the application
No response
Website URL
https://www.runatlantis.io/
Roadmap
https://github.com/runatlantis/atlantis/milestones
Roadmap context
No response
Contributing Guide
https://github.com/runatlantis/atlantis/blob/main/CONTRIBUTING.md
Code of Conduct (CoC)
https://github.com/runatlantis/atlantis/blob/main/CODE_OF_CONDUCT.md
Adopters
https://github.com/runatlantis/atlantis/issues/2626
Contributing or Sponsoring Org
No response
Maintainers file
https://github.com/runatlantis/atlantis/blob/main/MAINTAINERS.md
IP Policy
- [X] If the project is accepted, I agree the project will follow the CNCF IP Policy
Trademark and accounts
- [X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF
Why CNCF?
Atlantis has been part of the IaC community for many many years and lately, after a few years dormant it has been reviving thanks to the work of the maintainers and the community, it is more than ever vitally crucial for many companies and individuals these days were there is more and more IaC adoption in the industry. But without a good supporting structure, Atlantis could potentially one day go dormant forever and it will fracture the long-lasting community that it has built. That is why we believe by donating the project to the CNCF we could get the much-needed supporting structure to the project and drive a richer contributor community.
Benefit to the Landscape
As I said before, the project has been a long-time key player in the community, and its role in IaC and cloud infrastructure is vital, we feel that CNCF is a natural fit for the project. Many CNCF projects actually run Atlantis to create their own infrastructure to actually deploy their own code to the cloud resources or to deploy other CNCF projects in their infrastructure. It is a key piece withing the cloud native infrastructure.
Cloud Native 'Fit'
The Atlantis project fits within the Automation/Configuration section on the CNCF alongside terraform, ArgoCD, and others. It uses the GitOps workflow to run terraform automation to then deploy resources to support different other types of applications like, Kubernetes, Argo and many others. It sits in a key part of the deployment workflow of many cloud native application.
Cloud Native 'Integration'
Atlantis runs primarily Terraform project in a GitOps workflow. Any Terrafrom project can be run through atlantis and be enhanced by the many features that it offers. Atlantis complements terraform in particular by moving the IaC to the left, closer to the developer so that the interaction with terraform happens in familiar tools to the developer.
Cloud Native Overlap
none I believe
Similar projects
ArgoCD
Landscape
I do not think we are listed
Business Product or Service to Project separation
N/A
Project presentations
N/A
Project champions
N/A
Additional information
The project owner has authorized us to submit the project and has made us the official maintainers.
https://github.com/runatlantis/atlantis/issues/3686
+1
+1
+1
@amye I see other projects that committed the application later than us have feedback about their projects and I'm wondering if there is any feedback for our project? do we wait for the review on Dec 12 to hear back? Thanks.
https://github.com/orgs/cncf/projects/14 has the queue of projects - we'll set up which projects can be reviewed for a vote in early December in anticipation of the December 12th meeting.
Hi @jamengual would you be able to present Atlantis to TAG App Delivery at one of our general meetings? I created https://github.com/cncf/tag-app-delivery/issues/474 to describe what you would present to us, and we'll share the presentation and recommendations back with TOC here. We meet the first and third Wednesdays of every month and though there are other projects presenting on 11/1 and 11/15 we could probably get Atlantis in one of those too. Alternatively 12/6 is still open. Thanks!
I can do any of those dates, and we can prepare a presentation for that. @joshgav
+1
+1
+1
+1
@jamengual could we put you down for Wednesday December 6? We have another project presenting on 11/15 now, and I think folks will want to discuss how Kubecon went in the 11/15 meeting too. I'd like Atlantis to have a good 20-25 minutes, which would work best on 12/6. Will that work for you and the team? Thanks!
Yes, I can do 12/6.
+1
+1
+1
+1
+1
+1
Given the nature of this project, should it be in the CNCF, or part of the OpenTofu project?
Atlantis presented to TAG App Delivery on 12/6, recording and notes are available here: https://github.com/cncf/tag-app-delivery/issues/474#issuecomment-1861676966
We asked if the project would fit better in OpenTofu; the group expressed concern that they wish to support both TF and OpenTofu, but we answered that this should be feasible within OpenTofu as well. A question for us is if OpenTofu intends to accept other projects and implementations too. (Note: a similar question keeps coming up for LF's OpenAPI foundation too.)
If not part of OpenTofu then the TAG believes that Atlantis would fit in CNCF's sandbox.
+1
+1
+1
+1
Atlantis presented to TAG App Delivery on 12/6, recording and notes are available here: cncf/tag-app-delivery#474 (comment)
We asked if the project would fit better in OpenTofu; the group expressed concern that they wish to support both TF and OpenTofu, but we answered that this should be feasible within OpenTofu as well. A question for us is if OpenTofu intends to accept other projects and implementations too. (Note: a similar question keeps coming up for LF's OpenAPI foundation too.)
If not part of OpenTofu then the TAG believes that Atlantis would fit in CNCF's sandbox.
Since the submission of OpenTofu to the CNCF alongside the TAG App Delivery classification. I think it would make sense to keep Atlantis on track for CNCF submission.
https://github.com/cncf/sandbox/issues/81
+1
+1
The TOC reviewed this sandbox application on January 23rd.
The TOC recommends the project engages with OpenTofu to understand if it would be a good fit as a subproject. This should clarify the open question also raised by TAG-AppDelivery (https://github.com/cncf/sandbox/issues/60#issuecomment-1861686056) regarding support for both OpenTofu and TF.
@rochaporto The open question seems to be whether OpenTofu will accept subprojects or implementations.
A question for us is if OpenTofu intends to accept other projects and implementations too.
It would not benefit the project or be a good fit to be a subproject of OpenTofu. This aligns with our goal of being vendor-agnostic as an IaC orchestration tool beyond Terraform and OpenTofu implementations. It is my opinion that the open question is further answered by OpenTofu's application to the CNCF's sandbox. cncf/toc#81
If not part of OpenTofu then the TAG believes that Atlantis would fit in CNCF's sandbox.