Hi Eric, Yes, I can confirm that I left mime digest on for several days and there were mails which I didn't receive. Note that regular digests aren't working for me, either. Currently the only

Today we announced that we will help sponsor Cloud Foundry Meetups, and outreach in general, by helping to fund travel for

perhaps see if the lattice instructions for private registries have any hints for you: http://lattice.cf/docs/private-docker-registry/ -- Thank you, James Bayer

Successfully deployed from a registry with a public cert. A registry with a private/self-signed cert fails at the stager. I've got the name of the registry in insecure_docker_registry_list and

Yes! Thank you. Now on to registry debugging. The command did enable it. Tom

I believe you need to enable it via the cli. cf enable-feature-flag diego_docker

Deployed via http://www.evoila.de/cloud-foundry/adding-diego-release-to-cloud-foundry-release-v212/?lang=en (with v214 and 1398).(thanks for the write up) All deployed. Sample go app, pushed and

Are you able to deploy the jar yourself using "cf push" if you build the jar yourself? Are you having trouble pushing the jar, or having trouble figuring out how to do that same thing in

Hi, I'm trying to assign cc.info.description and cc.info.version [1] (to merge meta.releases[0].version if cf release version), as to be able to describe to end users which cf version is currently

There are additional use cases should also be considered. First, if I upgrade a service, that may come with a new management console on a different url, I would want this to be

How to auto deploy a jar file using travis into cloudfoundry My jar is built using ant .I have published my code and travis able to build the code automatically ,but i am not sure how to auto deploy

Hi All, As we worked on better documenting how app usage events and service usage events work [1] in the cloud controller api, we uncovered that service usage events do not currently expire

Hi Marco, We instrumented the collector and found that none of the existing CF components provide any tags which would be overridden by the latest collector change. So this change shouldn't affect

Thanks Marco - for everyone else on the list, we reached out to Marco after this email, and opened a tracker story[1] to do deeper analysis of collector tags that may change. Thus far we have found

Dear Erik, thanks for the detailed explanation and the heads-up. A few comments and questions below.

Hello Robert, Unfortunately, your use use case is not currently supported. dashboard_url is only supported in the initial response from the broker, even though the service instance may be

Hi Swatz, In your config file, you will have to use 'datadog-firehose-nozzle' as the username and the password you specified when you created the uaa client. And no, there is no need to restart

Why, yes, yes it does. Somehow missed this feature. Thanks! //Simon

simon, are you aware of the environment variable groups feature [1]? does that capability address this need to consistently expose env variables to all apps across the

Hi all, The loggregator team has been working to maintain metric parity between the CF collector[1] and the firehose[2] in the short term.This is to help CF operators feel confident they can move