Igor Zalutski
Igor Zalutski
Suggested behaviour by user: fail CI check in case of failing to acquire lock so that PR cannot be merged. It seems that we had it initially, then changed to...
From the user discussion @Spartakovic > ... when github triggers action on comments it’s using workflow file on the default branch, meaning it will use action version that is set...
A group of needs related to state manipulation (like manual importing, but other operations too - see related issues) seem to be shaping up from user discussion: "... when terraform...
Surfaced in the discussion with @SalvoRusso8 Comment by @Spartakovic: It’s a bit all over the place currently unfortunately - Aws: You can configure lock with either DIGGER_ prefixed keys, or...
TF version can be specified in digger action so why are we making user to install it by hand? Can bundle like other sub-actions From Allianz demo @motatoes
Different projects might require different versions of Terraform Use case at Wise as shared by Pavel
While debugging #111 the likely cause is DynamoDB resource mismatch It could be addressed by fixing #112 - but creating a separate one just to make sure that DynamoDB specifically...
To make things like [#111] easier to debug Can so far thinking of the following info that can be useful: - which cloud provider? - which CI provider? - call...
Opinions differ on this; see [merge-apply dilemma](https://itnext.io/pains-in-terraform-collaboration-249a56b4534e) - Some prefer to iteratively apply on a branch, then merge once - Others prefer to only deploy from main, creating additional fix...