digger

Digger is an open source IaC orchestration tool. Digger allows you to run IaC in your existing CI pipeline ⚡️ (by diggerhq)

Digger Alternatives

Similar projects and alternatives to digger

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better digger alternative or higher similarity.

digger reviews and mentions

Posts with mentions or reviews of digger. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-01-15.
  • GitHub issues from top Open Source Golang Repositories that you should contribute to
    8 projects | dev.to | 15 Jan 2024
    I would be extremely grateful if you could give us a star & share your thoughts in the comments section below https://github.com/diggerhq/digger
  • Tools used by the top 1% of Platform Engineers and their Commercial Open Source Alternatives
    3 projects | dev.to | 12 Jan 2024
    Check Digger's repo on GitHub
  • 5 Open Source tools written in Golang that you should know about
    5 projects | dev.to | 15 Dec 2023
    Digger is an Open Source Infrastructure as Code management tool that helps orchestrate IaC such as Terraform & OpenTofu within GitHub Actions. Digger reuses compute used for application code so that you don't overpay for 3rd party managed compute for IaC. This approach eliminates the duplication of CI/CD infrastructure such as compute, jobs, and logs, and reduces security concerns by keeping sensitive data within the CI job. Digger's integration with existing CI systems offers scalability by leveraging on-demand compute resources and enhances security by confining data within the existing CI environment.
  • Top 10 terraform tools you should know about.
    10 projects | dev.to | 11 Dec 2023
    Digger is an Open Source IaC management platform that allows you to orchestrate terraform/OpenTofu in your CI/CD system. It helps you resue async jobs infrastructure with compute, orchestration, logs, etc of your existing CI. Digger also has a pro version built on top of Digger’s community edition. Digger’s “bring your own compute” ensures that users have private runners by defualt and don’t have to pay for it additionally. Digger pro gives team leads, managers and IaC practitioners dashboards, Drift Detection, RBAC via OPA policies and concurrency so they can help guide the team.
  • OpenTF Announces Fork of Terraform
    28 projects | news.ycombinator.com | 25 Aug 2023
    - https://digger.dev/ - https://github.com/diggerhq
  • OpenTerraform – an MPL fork of Terraform after HashiCorp's license change
    10 projects | news.ycombinator.com | 11 Aug 2023
    To copy the comment from Reddit https://old.reddit.com/r/Terraform/comments/15o9mzt/openterr...

    > Funny enough, our own product (Digger, an open-source CI runner for Terraform) is not using Terraform (or any other Hashicorp's code) under the hood.

    Oh yes you are:

    https://github.com/diggerhq/digger/blob/develop/pkg/core/ter...

    You're on thin ice if you want to argue whether forking a terraform process constitutes "hosting" or "embedding" terraform.

    10 projects | news.ycombinator.com | 11 Aug 2023
    We are in some sense a competitor too, alongside Spacelift, Env0, Scalr and a few others. Our product is built differently though, Digger is orchestrating terraform jobs in your existing CI instead of taking over the whole CI stack and effectively duplicating it just to run terraform. We built it this way almost by accident; our original product was very different (think "heroku-like UI for AWS" that generated and ran terraform on the server) and this is how we arrived at what Digger is now. Luckily we don't seem to be affected by the licensing change as we neither embed nor distribute any of hashicorp's code (it's on the user to set up the right version of it in say GH Actions).

    https://github.com/diggerhq/digger

    Anyways, fully agree that if you have a great product, you don't need to make such moves. We designed our product the way we did purely out of technical considerations - it didn't seem to make any sense to duplicate the CI stack. But it looks like this whole idea behind Terraform Cloud of having an "infra-specific CI" was driven exclusively by commercial interest. You can charge per minute! You can charge even more per resource! Now it's catching up with Hashi; so they have to make such defensive moves. If the product made sense technically, if it was designed the way someone would design it with no commercial considerations whatsoever, they wouldn't have to make such moves.

  • FLaNK Stack Weekly for 17 July 2023
    13 projects | dev.to | 17 Jul 2023
  • Terraform Tower
    7 projects | /r/Terraform | 12 Jul 2023
    Digger
    7 projects | /r/Terraform | 12 Jul 2023
    One of the founders of Digger here (thanks everyone for mentioning us!) We are an open-source CI/CD tool for Terraform - just like Ansible Tower
  • A note from our sponsor - LearnThisRepo.com
    learnthisrepo.com | 26 Feb 2024
    LearnThisRepo lets you learn 300+ open source repos including Postgres, Langchain, VS Code, and more by chatting with them using AI! Learn more →

Stats

Basic digger repo stats
84
2,573
9.8
3 days ago
Learn 300+ open source libraries for free using AI.
LearnThisRepo lets you learn 300+ open source repos including Postgres, Langchain, VS Code, and more by chatting with them using AI!
learnthisrepo.com