Hello, I am trying to setup Cloud foundry environment on Eclipse, so that I can make java project and deploy them directly to the Cloud Foundry(Server), But due to mismatch in different plugin

I am getting error while running data-dog-nozzle - https://github.com/cloudfoundry-incubator/datadog-firehose-nozzle go run main.go -config

What do you mean by "after restarting cf"? How are you doing that? There's a lot of components, which one or ones are you restarting? What steps are you running? Dan wrote:

Hi all, We tried to update the default buildpacks with a new version. However, after restarting cf, the old version comes back. (See below) It seems all the default buildpacks will be ensured to be

Hi Qing, First, Ops Metrics is a closed-source addition to Pivotal Cloud Foundry. The metrics exposed by Ops Metrics today come from the collector[1] and tomorrow from both the collector and

i'm glad you found it! i'll make sure that amit gupta sees this report as he is currently PM for the MEGA team that is responsible for the DEAs. thanks for sharing the results. -- Thank you, James

Finally, I find out the problem, but may not the one I said above. It seems a little bug exsited. In my deployment, it will install some buildpacks by default, but perhaps caused by some network

yes, it work before.

Hi, You never change the password right ? it was working before ?

Is refresh token always returned, for all the grant types ? It seems to be the case for authorization_code grant type but I don't think it is returned for client credentials

Hi all, We've recently announced CF Summit events for both Berlin and Shanghai, and we'd love your participation! Berlin will be on November 2nd and 3rd, 2015 > http://berlin2015.cfsummit.com/ The

Hi Mike Thanks for addressing my questions gain. I agree that it's important to make both the rootfs and the buildpacks backward-compatible with each other. People often use master branch of the

Hi Jack, Thanks for asking these questions. Not knowing what specific changes you're referring to, I'll try to address some different aspects of the topic. First, just to set expectations, `lucid64`

That did the trick, thanks Filip. Using Basic auth, cf as client id and an empty password is the solution Keagan

I notice that there are a few changes going into the rootfs [1]. Are there corresponding changes in the buildpack which would make them unable to work properly in older levels of the rootfs (both

I set up the open source CF and got the metrics streamed out of the firehose. I also read document about Pivotal Ops Metrics in

cf client is fine. put empty string as a password Filip wrote:

So we're just using the cf client which doesn't have a secret defined, is that why we need to use the admin client? -- View this message in context:

Your authorization header should be Basic (meaning, you need the client id and secret to retrieve the refresh token)

Simple test that does what you need https://github.com/cloudfoundry/uaa/blob/develop/uaa/src/test/java/org/cloudfoundry/identity/uaa/integration/RefreshTokenSupportIntegrationTests.java#L147-L150 we