Mateusz Kowalczyk

@sternenseemann Oh, I wasn't clear. We have our own package that _directly_ depends on `assert` (`assert` was written by our former co-worker, it may have even been written while he...

Having said that, it is still possible to add extra policies to the role that the module creates. For example: ```terraform module "gitlab_runner" { … } data "aws_iam_policy_document" "gitlab_runner" {...

@krzysztof-miemiec I'd just like to check the status: do you plan to work on updating this PR and getting it merged in? Have you decided to not pursue this?

I've been trying this out today. It seems quite nice so far though I've only just started. I should say that I never used `terraform-aws-gitlab-runner` before and am starting from...

A bug report: currently we have ```terraform data "aws_subnet" "runners" { id = var.subnet_id_runners } data "aws_availability_zone" "runners" { name = data.aws_subnet.runners.availability_zone } … aws_zone = data.aws_availability_zone.runners.name_suffix … "amazonec2-zone=${aws_zone}", ```...

Another report: applying today I got `Error: Error creating CloudTrail: InsufficientS3BucketPolicyException: Incorrect S3 bucket policy is detected for bucket: ` so there seems to be some race condition as re-running...

w.r.t https://github.com/npalm/terraform-aws-gitlab-runner/pull/249#issuecomment-741572105 >A fix is to simply allow aws_zone be set per runner: Please ignore this. You can do exactly that (set `aws_zone` for the runner) and it works properly....

Another thing: The whole CloudWatch event machinery to pull in a new runner configuration does not work unless SSM is enabled (`enable_runner_ssm_access = true`). Without this, the instance is never...

>This can mean that each of the registered runners will have its own token. Not only does this allow to tag each executor in a different way, there is an...

Another report: changing the `gitlab_runner_registration_token` we have deployed once before has no effect. This is because when we initially registered with this value, in user_data we put the result in...