Adrian Grucza

I had the same problem. After moving my Go code into the proper location (a directory under $GOPATH/src), the problem went away.

Yes, it does seem that go-mutesting doesn't really support projects with Go modules and this needs to be fixed. The only way I've found to work around this problem is...

@gwatts it's because the build script you ran does not exclude `devDependencies`, so the `node_modules` directory contains modules that get unnecessarily included in the package. You should not need to...

Just added a commit - `build.sh` now excludes `devDependencies` too

> Is there a CFN template, or Terraform that creates the secrets in Systems Manager and deploys the lambdas? I do have Terraform for this. It's currently in a private...

@bsneider I didn't include a module for the CloudFront distribution because it would not add much value over the [aws_cloudfront_distribution](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudfront_distribution) resource itself. I could add a CloudFront example to the...

I've added example CloudFront Terraform to the [examples](https://github.com/iress/cloudfront-auth/tree/master/infra/terraform/examples) directory

I found that SonarQube has a [generic issue import format](https://docs.sonarqube.org/latest/analysis/generic-issue/) that is better than the linting report formats because it gives you full control over issue fields and values, e.g....

I've created a PR here: https://github.com/stryker-mutator/mutation-testing-elements/pull/2044

Thanks, I've updated the jq filter to better handle missing values and added it to [mutation-testing-elements/](https://github.com/stryker-mutator/mutation-testing-elements/). Instructions on integrating with SonarQube are now on the website: https://stryker-mutator.io/docs/mutation-testing-elements/sonarqube-integration/