Igor Zalutski
Igor Zalutski
Currently Digger does neither provide drift detection, nor facilitates it Approach suggested by Karl Taylor @ Bitmex: ability to run a cron-like job to check for drift with smth like...
Raised by Bastien: regarding terragrunt, I think you don't have the concept of dependencies yet. Right now I'm parsing hcl files to generate digger.yml with the correct include_patterns . Is...
Regroup comments about locks being acquired / released, multiple apply outputs, and failing apply comment.. Think it would be even cleaner and consistent raised by Bastien
Currently the only way to configure the function to trigger the pipeline on Azure is by providing a PAT Raised by @mtb-xt
when auto-commit is set to true, no Github Action will be triggered, and so whatever is configured in on_commit_to_default is not executed (only when merged manually) Q: is that some...
There is currently no way to prevent people running apply from comments, even if apply-on-merge is configured Flagged by @Spartakovic in relation to the apply-on-merge [docs](https://docs.digger.dev/configuration/apply-on-merge) requested by someone on...
Full commit logs is nice, but having consolidated view be good - to see relevant information
Given that we now store plans, it might be useful to show the diff of plans in the PR (previous vs latest) The challenge is that plan is non-deterministically ordered...
It appears that stored plans don't have unique IDs (see attached screenshot)  Raised by @fleroux514 > If run digger plan , which succeeds and stores the plan file...
It could be useful to have in the docs a policy with minimum permission required for S3, as done for DynamoDB here: https://diggerhq.gitbook.io/digger-docs/aws-specific/setting-up-dynamodb-access-for-locks Raised by @SalvoRusso8