digger
Pitaya
Our great sponsors
| digger | Pitaya | |
|---|---|---|
| 85 | - | |
| 2,647 | 845 | |
| 2.8% | - | |
| 9.9 | 0.0 | |
| 6 days ago | over 4 years ago | |
| Go | Swift | |
| Apache License 2.0 | 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.
digger
-
Ask HN: Should we build support for more CI platforms, or features for Actions?
Currently, Github Actions is de-facto the only fully supported CI platform in Digger, we’ve been building it as a CI-agnostic tool (https://github.com/diggerhq/digger) from get go. We keep getting requests to support more CI systems on our community slack and over Github issues (https://github.com/diggerhq/digger/issues/81).
Unlike other automation tools for Terraform, Digger doesn’t run jobs on the server; instead it uses your CI (like Actions) as a compute backend. This is more secure and also much cheaper if you use your own runners in your CI.
But each CI and each VCS is ever so slightly different; and we are now at a crossroads - Should we build support for more CI platforms, or more features for GitHub Actions? We’d love any thoughts/inputs!
-
Ask HN: Should open-source projects allow disabling telemetry?
We just had a user submit an issue and a PR to revert the changes we made earlier that remove the option to disable telemetry. We feel like it’s a fair ask to share usage data with authors of an open-source tool that’s early in the making; but the user’s viewpoint is also perfectly understandable. Are we in the wrong here?
https://github.com/diggerhq/digger/issues/1179
Surely we aren’t the first open-source company to face this dilemma. We don’t want to alienate the community; but losing visibility of usage doesn’t sound great either. Give people the “more privacy” button and most are going to press it. Is there a happy medium?
-
Terraform drift detection and remediation - a primer
Detecting and managing drift in Terraform is a multifaceted process. The use of Terraform commands such as terraform refresh and terraform plan plays a critical role in identifying drifts. Additionally, periodic monitoring of the infrastructure using these commands can aid in early detection and prevention of larger issues. Tools like Digger and Terraform Cloud offer dedicated drift detection and remediation mechanisms. These tools provide continuous monitoring and notifications, enabling teams to stay informed about the state of their infrastructure.
-
Typical challenges faced while setting up CI/CD for Terraform at scale
Star us on GitHub | Check out Docs | Blog | Slack
-
GitHub issues from top Open Source Golang Repositories that you should contribute to
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
Check Digger's repo on GitHub
-
5 Open Source tools written in Golang that you should know about
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.
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.
-
Restricting apply permissions
We have this issue filed by a user and cannot quite decide internally what to do about it. It is clear that allowing everyone who comments to trigger apply is problematic. And we have this covered by the RBAC via OPA feature that allows users to set granular rego policies for who can do what. But it can also be viewed as an overkill to introduce the whole policy-as-code setup for a basic restriction like this.
- Digger - Open Source Terraform & OpenTofu automation tool for teams (Runs within GitHub Actions so you don't pay for 3rd party compute)
Pitaya
We haven't tracked posts mentioning Pitaya yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
atlantis - Terraform Pull Request Automation
Digger - Digger is a lightweight download framework that requires only one line of code to complete the file download task
terrakube - Open source IaC Automation and Collaboration Software.
Alamofire - Elegant HTTP Networking in Swift
terrateam - Terraform automation for teams. Purpose-built for GitHub.
APIKit - Type-safe networking abstraction layer that associates request type with response type.
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
Swift-Server - A very basic proof-of-concept Swift HTTP server that does not require Foundation
otf - An open source alternative to terraform enterprise.
RealReachability - We need to observe the REAL reachability of network. That's what RealReachability do.
iTorrent - Torrent client for iOS 9.3+
Moya - Network abstraction layer written in Swift.