Soham Parekh’s first day at Digger was Monday, June 30. He applied to our Founding Engineer role; his profile clearly stood out. Little did we know at the time what was hiding behind his resume! For those of you who don’t know - Soham turned out to be| Digger.dev
Introduction AWS Bedrock is Amazon's fully managed service that makes foundation models from leading AI companies accessible via an API. For organizations looking to integrate generative AI capabilities into their applications, AWS Bedrock provides a streamlined path to leverage powerful AI models. When combined with Terraform, an Infrastructure| Digger.dev
In the IaC world – infrastructure drift refers to a situation where the actual state of the infrastructure differs from the desired state defined in your IaC configuration, such as a Terraform/OpenTofu configuration. Drift can occur due to a variety of factors, including manual interventions, updates from other services,| Digger.dev
Infrastructure as Code has revolutionized the way organizations in the enterprise manage and deploy their IT infrastructure, with Terraform/OpenTofu standing out as a popular tool for defining and provisioning infrastructure across multiple cloud providers. This was also reflected in the latest GitHub Octoverse report, here's a quote| Digger.dev
Managing Terraform workflows efficiently can be challenging, especially when working with a team. While Atlantis has been a popular choice for Terraform collaboration, it comes with its own set of complexities and maintenance overhead. Enter Digger: a robust, production-ready atlantis alternative for terraform automation that integrates seamlessly with GitHub Actions,| Digger.dev
When working with large monorepos, managing Terragrunt plans can become overwhelming. Each project generating a comment in the pull request can result in a flood of information, making it challenging to track changes effectively. This is where Digger's feature to group plans by the source module comes in| Digger.dev
What is Buildkite? Buildkite is a powerful CI/CD platform designed for flexibility. It enables development teams to automate their build, test, and deployment processes using a customizable pipeline. One of Buildkite's features is its ability to run self-hosted agents, which can be deployed on any infrastructure, including| Digger.dev
Developers looking for efficiency and automation to simplify project setup and deployment is (supposed to be) a “need” we already know about. Recognizing this need, we introduced a a functionality in Digger, tailored to enhance project initialization and setup for Terraform projects. This functionality, known as generate_| Digger.dev
Overview In this article, we will explore how to deploy a RAG chatbot app that interacts with large language models(LLM’s) to a cloud provider such as AWS using GitHub Actions, OpenTofu, and Digger. We were extremely inspired by Wenqi Glantz' article and thought of creating| Digger.dev
While talking to users using Digger in GitHub Actions, we see a lot of compliance heavy enterprises relying on Self Hosted runners. We decided to compile a list of available solutions out there, to help present the options available before a decision is made. Let's dive in: Actions| Digger.dev
This was meant to be just another feature announcement post. Something along the lines of “you can now run Digger CLI on your laptop; here’s why this is cool” kind of post. But as I started writing it I realised that why we built this feature is just as| Digger.dev
We often get asked this question. The answer is simple - the orchestrator backend for Digger does not necessarily need to be publicly accessible, but it does need to interact with GitHub to trigger CI jobs. So basically, whether you choose to self-host Digger or use the managed Digger Cloud| Digger.dev
This is something that we get asked very often. Integrating Terraform into GitLab CI clearly offers a streamlined approach to manage and automate infrastructure deployment, and infra engineers are always curious and keen to POC this to their peers. The reason is clear - cloud credentials never leave the privileged| Digger.dev
We wanted to document learnings from launching our devtool (and multiple acquisition products) over 14 times on Product Hunt, and that is what this article seeks to do. We have learned a ton in that period (May 2022 - Jan 2024) and also pivoted 4 times in the process. This| Digger.dev
What would it take to migrate away from Terraform Cloud? After Hashicorp moved to resource-based pricing and BSL license last year, this question is on the roadmaps of many infrastructure teams. This article outlines the scope of such a migration. In this article I will describe the main aspects of| Digger.dev
How we are designing Digger to support multiple CI's for Terraform plan & apply, ensuring users don't pay for compute twice, and enable RBAC.| Digger.dev
Introduction OpenTofu offers a versatile command-line interface for managing your infrastructure. With a diverse range of commands, you can initiate, validate, and manipulate configurations with ease. Command Basics: Run the tofu command by itself to get a list of available commands and their purposes. The general structure is: tofu [global| Digger.dev
Unpacking the Business Source License (BSL), its implications in the open source realm, Hashicorp's shift, and the proposed Open Charter solution| Digger.dev
The following resources have been collated to help IaC users get a better understanding of how Infrastructure as Code can be run within their CI/CD system of choice. Do have a read! Circle CI 1. How to run Terraform from Circle CI by Anton Putra 2. Tom Hipwell @ Bulb| Digger.dev
Running Terraform in Jenkins involves setting up a Jenkins job or pipeline to automate your infrastructure provisioning and management. Here are the general steps to run Terraform in Jenkins: Prerequisites * Install Jenkins: If Jenkins is not already installed, you need to install it on a server or a suitable environment.| Digger.dev
