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

Hi Yitao, I would recommend either using manual networks, or following the GitHub issue Ben R created above to see if the BOSH team can figure out the root cause of this issue with dynamic

Rather than continue this discussion here I've created an issue stating my case here: https://github.com/cloudfoundry-incubator/executor/issues/17 Mike

Hi Troy, I agree that we should bring our buildpack implementation up to date with Heroku's by adding the .profile runtime hook. Also, I believe Eric Malm had some thoughts on this hook, and how we

I think many of the use cases *could* be dealt with by multi-buildpack support or in a forked buildpack which executes the desired commands. However, the point of the feature is to allow the addition

Thanks, Mike. If source-side processing is the right place to do that \u2028-to-newline substitution, I think that there could also be a config option on the dropsonde library to have its LogSender

Credit to Jan Dubois, who actually drafted the document, and who will be helping me respond to your comments in the document. I'll provide concrete use cases where possible. The ones I have

Thanks for the insight Jim. I still think that the Executor is the place to fix this since multi line logging isn't a Loggregator limitation it is a log inject limitation which is owned by the

Hi Sylvain, It looks like your problem might be that one or more of the consul certificates in your cf manifest is not a valid PEM encoded certificate, or the certificates are missing entirely. Do

For those who have pipelines that run DEAs and HM9000, you will need to update your manifest to include certificate information. For CF users that consume releases, this will only apply once it makes

In traditional environment, we have massive physical servers hosting database and indexing engines (e.g. solr). How can we achieve similar results with small footprint but large number of