Mateusz Kowalczyk

Another issue: ```terraform # module.gitlab_runner.aws_cloudwatch_log_group.environment[0] will be created + resource "aws_cloudwatch_log_group" "environment" { + arn = (known after apply) + id = (known after apply) + name = "…" +...

Today I realised there is very easy way to simplify the whole thing and have multiple executors. The main problem is about synchronising config against some source of truth. really,...

I've made a start here https://github.com/tsurucapital/terraform-provider-gitlab/tree/gitlab-runner-register This allows to register each executor/runner via terraform separately and get tokens for each which was probably the biggest hurdle. With that, we don't...

Hm, fair enough, but I imagine aeson maintainer should make the package as they'll be able to update it with any aeason changes accordingly.

How about putting the newtype in base64-bytestring and adding dependency on base64-bytestring in aeson which can then provide instances? I think it's either that or creating a package solely for...

AFAIK the "canonical" solution to this for last few years is `ByteString64` newtype though I would still like it to live inside aeson as `ByteString` instance as it's often a...

if you want different encoding then you can use newtype, this issue is about having a default

it's no different than `blob :: ByteString64, hash :: ByteString64` except now you need an instance for every one of your wrappers (Blob, Hash, …) that you have to write...

I don't suppose there's a way to make this issue prioritized, like financial donations &c.?

Understood, thank you.