Christian Jensen

Solved with: 😅 ``` terraform { required_version = "> 1.0, < 1.2.7" } ``` Totally tongue in cheek but yea, I really had to do this - everything I ran...

If you are still looking for examples of what was failing... ``` module "log_bucket" { source = "registry.terraform.io/terraform-aws-modules/s3-bucket/aws" } ``` No `version` applied.

I agree with this as well. I do wonder however, how do you ever trigger the `meta.theme` to be used as it is not very clear. Thus far it seems...

Just use Snyk - dependabot clearly does not care about Terraform.

I would love to get this working.

I just encountered this issue or something remarkably similar. Is there a fix for this? ``` => ERROR [build-stage 7/7] RUN npm run build 1.5s ------ > [build-stage 7/7] RUN...

My implementation was an afterthought. I had already created the whole magic link flow and realized that it would be far too easy to leak out the url to someone...

I have a little more information on this - It appears that this check was created because of different parsing problems. There are times when the column names are not...

Additional note for whomever is watching along, we are having to abandon the use of Replibyte. There are far too many issues and we cannot proceed: * Cannot leverage multiple...

I had a few other things in addition to the inline cache issue - I have decided to go back a version. Sharing how I did it here in case...