Igor Zalutski

Suggested by Bikram Das

Also flagged by Karl Taylor @ Bitmex as need

Suggested by @Ido-Ozeri

Thanks for the idea!! Tagging @veziak @Spartakovic for input

Adding the underlying problem flagged by @fleroux514: "One feedback from the team is that is generates a lot of PR comments."

@fleroux514: "Wondering if we it could even go one step further and also regroup comments about locks being acquired / released, multiple applyoutputs, and failing apply comment.. Think it would...

hey @daanbosch thanks for filing the issue! did you add your cloud provider keys as secrets in the action? (assuming you are using it with Github Actions) also - what...

Looking into it! Also created an issue to improve debuggability (above) So far it seems to be coming from here: https://github.com/diggerhq/digger/blob/46a2a6d8dc45591c73885943a3faa97723f3cf43/pkg/digger/digger.go#L233 from there its either GCP locking provider or AWS...

Ok we were able to isolate it to AWS locks implementation as the most likely source. It suggests that the DynamoDB table for locks likely wasn't created: https://github.com/diggerhq/digger/blob/46a2a6d8dc45591c73885943a3faa97723f3cf43/pkg/aws/dynamo_locking.go#L50 One possible...

Okay then it's likely something wrong with the DynamoDB expression building here: https://github.com/diggerhq/digger/blob/46a2a6d8dc45591c73885943a3faa97723f3cf43/pkg/aws/dynamo_locking.go#L43 We will obviously refactor this (#113) - but for the time being, can you share the entries...