Igor Zalutski
Igor Zalutski
Currently after app is installed, we expect digger.yml to be pushed to get projects. But what if it's already there? Non-obvious step
Planning on every commit in draft PRs before they are marked as ready for review is not economical, and noisy. > We have a lot of PRs created as Drafts,...
I’m trying to generate terragrunt project but also be able to assume different roles for specific projects, but I can’t get the roles to switch. I’m guessing something is wrong...
Digger feels slow; Francoi's suggestion is that we might not be using Github cache for terraform dependencies, so it always runs init from scratch
We could show more useful info when user clicks "details" in the check; likely by using newer checks API Currently, it goes to Action run screen Other tools: - TFC...
Currently, Digger sends drift alerts via Slack only. This however makes them just FYI - there is no way to trace what happens to each alert, other than threads or...
User: I have been testing Digger with backend, but on every PR ( even with just adding an empty line) a GHA job would run just to tell me No...
> Wouldn't be more practical if the checkov tests results including both Failed and Passed are commented in PR, as it would be easier to read what has to be...
Why do we even need DIGGER_TOKEN? Why not just use GitHub app as-is, without additional digger auth on top? The reason we built it this way was to enable Digger...
Users currently need to specify `digger-organisation: 'digger'` in digger.yml, and there is also a toggle at the bottom left on the login page. There is however nothing that the users...