Show HN: Digger – an Open Source Terraform automation and collaboration tool

Re:Show HN: Digger – an Open Source Terraform automation and... by lantry on Sunday July 09, 2023 @03:30PM (#36658010)

I was initially very interested in digger, because I need something like atlantis but the thought of a web-accesible server with owner-level access to my project seemed scary. Having everything in cicd seemed like a great solution. However, when I read the digger docs, I discovered that it too has a publicly accessible server, that gets autodeployed when you first run digger.

1. I don't like the idea of the tool creating resources I didn't explicitly tell it to create

2. I don't like the idea of a public endpoint for someone to pwn and get owner-level access of all my stuff.

It would be nice if the docs explained what the serverless backend thing does (besides the vague comment about handling webhooks), and it would be nice if there was an option that didn't require the public backend even if it means slightly degraded functionality. (github actions can be triggered by PR opened, PR updated, comment created, comment edited, merge to main, and many other things. Seems to me like that should be enough?)

https://docs.digger.dev/readme/how-it-works

[ Parent | on HN ]

Re:Show HN: Digger – an Open Source Terraform automation and... by izalutski on Sunday July 09, 2023 @07:16PM (#36660084)

All valid points! Thank you!

We were initially completely backend-less; but then it increasingly became apparent that a central orchestrator is unavoidable.

Rationale here: https://diggerdev.notion.site/Why-digger-introduces-an-orche...

In hindsight, it makes sense that literally every single other tool in the space has a central backend that orchestrates jobs. There's a good reason for that.

To address security / access concerns, you can either self-host the orchestrator, or use OIDC, or both

[ Parent | on HN ]