Martin Chvíla

Let's say I have a PR opened with changes in 10 TF modules. Digger runs plan for all of them and creates a comment with plan summary. I will get...

Right now I have to do the updates by deleting the row in DB and using API call or editing in DB.

Still valid as of v0.4.9.

Still an issue as of 0.4.13. I think the issue is in the generated SQL command ``` UPDATE "policies" SET "policy"='package digger default allow = true ',"updated_at"='2024-01-10 10:43:41.073' FROM "policies"...

> There is at least one other user who didn't want to use Gitlab's (not Github's) artifact storage for plan files, citing security reasons. I would love to better understand...

Was this fixed? I am no longer getting the error since v0.3.19 (might be fixed in earlier).

Great, I wanted to suggest the same. My use case is to use different github workflow files per environment (DEV/PROD), to setup different github runners config and different roles. What...

Yes that would be great! It's only a cosmetic to have more less lines in the digger.yaml for me though, I am happy also with the current implementation, that enables...