Tell us about your terraform automation tooling before Digger.

We used another terraform automation tool in our Github actions, but there were many inconsistencies and the tool has started implementing pricing that wasn’t suitable to us. The community wasn’t as active as we’d have liked it to be either. 
We were in pursuit of an alternative that was Open Source, had a more active and bigger community with an active support channel. Moreover, since the community edition was sufficient for our use case, using Digger would effectively be free for us.

Walk us through the experience taking Digger into production.

Digger has proven to be a valuable tool in our production environment, delivering an experience that aligns with our use case. Its integration into our workflow for PR reviews has been extremely helpful for us as a platform team. We rely on Digger regularly for reviewing pull requests, and it has streamlined this process to the point where we're able to conduct thorough reviews more efficiently than ever before. This efficiency has, in turn, accelerated our entire shipping process, allowing us to deploy updates and new features with greater speed and confidence. The overall impact on our productivity and output quality has been substantial, making Digger an essential part of our development toolkit.

What would you miss the most if you had to stop using Digger?

If we were to stop using Digger, the feature we'd miss the most would undoubtedly be its highly efficient and easily accessible PR review functionality. Digger's performance is also particularly noteworthy; it's faster and more responsive than any comparable tool we've previously utilized. This speed doesn't just save time—it also enhances the quality of our reviews by allowing us to iterate more quickly and catch issues earlier in the process. The ability to execute comprehensive PR reviews without delays has had a direct impact on our team's productivity and the overall velocity of our releases.

How was the help when you ran into problems?

The availability of prompt support through Slack channels has been a significant advantage, even when using the open-source version of Digger. The community, alongside the core development team, actively monitors these channels, ensuring that technical inquiries and issues are addressed efficiently.

Describe Digger to a friend in one sentence.

“In simple words, it can be compared to a CI/CD pipeline for your terraform code”