Tim Davis

@Minigugus Ok! I think we are all set 🔥 ⌨️ 🔥

Yes I will tackle it sometime this week 👍

@porsager thank you, the conflict has been resolved :salute:

Hi @porsager @Minigugus I believe we are all set, but I'm not really sure why CI failed, it seems to have completed successfully on my own CI https://github.com/thebearingedge/porsager-postgres/actions/runs/3079235630

Hi @akatechis, The `types` option will need to be an object, like this example under Custom Types. https://github.com/porsager/postgres#custom-types your interface PgTypes, will need to have a separate key for each...

@akatechis no worries 😄 regarding your custom `string` type. for that you will need to define it as a domain, as i do not believe that postgres has it. there...

In case it helps, I have opened #172

Curious about this as well. I've had trouble using the full `docker.io/some-namespace/some-image:tag`. example: ```hcl # works fine data "docker_registry_image" "coredns" { name = "coredns/coredns:1.11.1" } # doesn't work even though...

The way `localtunnel` works is that [the client](https://github.com/localtunnel/localtunnel/blob/master/lib/Tunnel.js#L62) sends a request to [the server](https://github.com/localtunnel/server/blob/master/server.js#L108) to set up a new TCP server, exclusively for that client. Then, the client connects directly...

I haven't taken the time to build a minimal reproduction but I did notice an error in either the API server pod or the scheduler pod. When applying an ingress....