Tom Kapanka
Tom Kapanka
Rather than an ETA, I'd be happy to know if it's being considered or worked on. If so, then I would know that eventually I can use it. For now,...
I inadvertently filed the same bug under the main Terraform repo. Pasting it here for reference: https://github.com/hashicorp/terraform/issues/31234 My workaround was to use `nonsensitive()` to get what I need working until...
`2016/08/02 17:04:43 http: multiple response.WriteHeader calls time="2016-08-02T17:04:43.813279646Z" level=error msg="Handler for GET /containers/json returned error: write unix /var/run/docker.sock->@: write: broken pipe"` $ docker -v Docker version 1.11.2, build b9f10c9/1.11.2 AWS/ECS AMI...
I'm also interested in this and suggest something along these lines: using a connection block inside the provider: ``` provider "consul" { address = "${aws_route53_record.elb_consul.fqdn}" datacenter = "dc1" connection {...
Checking back in on this. Would love to see this someday! Also, I can confirm the plugin works great as a stopgap measure until native support is added! Great work...
For anybody else running into the same issue, this is the config that eventually worked for me to get the namespace create job to run with TLS: ``` values: admintools:...
Having just gone through the process of creating certs and CAs for Temporal, this is a welcome piece of work. Thanks @luismacosta! Can you elaborate a little on what `isCA`...
Just running into this as well when we switched from letsencrypt prod to stage issuers for development clusters, and I could no longer provision our Zitadel environments with Terraform. I...
https://github.com/zitadel/zitadel/issues/10142