boarder981

Agreed. Great tool, but has some serious flaws/bugs in my experience (see [this article](https://github.com/breser/git2consul/issues/177) for specifics)

Anyone have thoughts or ideas on how to fix this? Just FYI - since I submitted the original post, I changed the polling interval for all of my projects to...

@tomhobson I'm not sure if this is a new feature since your last comment, but Azure DevOps does have support for pull requests -- https://docs.microsoft.com/en-us/azure/devops/repos/git/about-pull-requests?view=azure-devops My team also uses Azure...

Same exact issue for me. Upgraded from Consul 1.0.0 to 1.1.0 and it totally broke my script checks.

> /remove-kind bug /kind support > > * If ssl-passthrough is configured then the use of the backend-protocol annotation makes no sense. The connection is passing through the controller, instead...

> As far as I know Ingress NGINX does not support PROXY protocol for upstreams, maybe not even NGINX itself does. So this approach can not be implemented anyway. This...

Exactly! I don't even care if the real IP makes it to the backend. I only want to prevent non-whitelisted IPs from making requests to certain ingresses on the external...