As an update, it looks like I’m running into the Node health flapping <https://github.com/hashicorp/consul/issues/1212> issue that is more frequent with consul 0.5.x servers compared to 0.6.x

Hi all, tl;dr We've introduced a breaking change to cf-test-helpers (https://github.com/cloudfoundry-incubator/cf-test-helpers), so be careful if you decide to update to the newest version in your

ClientAuthenticationFailure ('Bad credentials'): principal=admin_ui_client your password for client admin_ui_client is incorrect

Recently I started using cloud foundry admin_ui .When I logging in I am getting Scope Error Insufficient scope for user while logging in.I followd all the steps in

Hi Sylvain, Good to hear, let us know if you have any other problems.

We passed the smoke tests by: * Only returning a 503 if the requested route exists. * Embed the old 404 page text in a comment of the returned html. Mike

Hi, Am 14.04.2016 um 13:23 schrieb James Leavers: This week we did basically the same - map application with a wildcard domain - change the errorpage - change the statuscode to 503 service

Thank you Amit for your answer. I ran again in the “all-consuls-go-crazy” situation today, as quite every day actually. As soon as they start this flapping membership issue, the whole cf+diego

wrote: There's two parts to this problem: 1.) You need to get metrics from the platform. I don't think (although this could have changed, since it's being rewritten at the moment)

wrote: Are you referring to the RemoteIpValve that is configured for UAA? https://github.com/cloudfoundry/uaa-release/blob/develop/jobs/uaa/templates/tomcat.server.xml.erb#L70-L73 Because the

https://docs.pivotal.io/pivotalcf/concepts/how-applications-are-staged.html you can check the curl messages by exporting environment variable CF_TRACE=true bharath wrote:

Hello! As the [official Go release policy]( https://golang.org/doc/devel/release.html) has deprecated support for Go 1.4, the Buildpacks team would like to propose the removal of Go 1.4 support from

The end of this presentation [1] from the CF Summit has an example of creating a wildcard route to route 404s to an app, using cf

Hi, i end up regenerating the whole stack using v234 instead and it worked - using the same consul certificates. Sylvain

Thanks Mike. Could you show me how can I do things like that, of if there are some document about it? If there are other ways to do that? Thanks, Stanley

I'm an idiot. I see what you and Eric are saying now. Put the code in Dropsonde then let the Executor simply initialize Dropsonde that way. Works for me. Thanks, Mike wrote:

My last 2 cents. It'll be configurable so will only be active in users of dropsonde that want the functionality such as the Executor. -- Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io |

You may want to reference the issue I created on executor. In that issue I note that I don't think dropsonde is the right place to do this token replacement because dropsonde doesn't know that the

We're going to look into it <https://www.pivotaltracker.com/story/show/117583365>. -- Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963

Hi, I have a pull request to warden repo to expose container termination timeout out to yml config. But I've been told that it needs to be discussed with Diego team since it can affect it and needs