I don't believe this is a bosh feature. Checked with Dmitriy and he confirms. Could you share any links that indicate that bosh supports that? We could look to improve the documentation in that area

For apps/services hosted on the system domain that get their route by publishing to nats or the routing-api, I believe it only requires registering the route with the additional route_service_url.

Our use case include restricting access to some hostnames on the system domain (e.g. api/login/etc.) as well as others that we may add externally. From a cursory read of the proposed spec it sounds

Woops, thought I was responding to Gabe. Disregard. :) wrote:

The routing team would like access! I see the OAuth is through Github, do you need github handles or can you add teams? - Chris wrote:

Hi all, We've enabled OAuth login to https://runtime.ci.cf-app.com Currently this is in addition to basic auth. We plan to eventually retire basic auth. The MEGA and CAPI teams have access via

Mike, Thanks for the quick reply. My question is more around using an 'online' buildpack vs. 'offline'. When I say 'online', I'm referring to the binaries being pulled from the s3 repo at staging

The blobstore properties in bosh allows you to enter an encryption key to encrypt the data before it is pushed up to an s3 bucket. In the cloud foundry deploy, can this encryption property be added

Hi Shawn, Thanks for asking. The actual URL used is going to depend on what version of the buildpack you're using. Currently master (v1.5.1) is only referncing CF-generated binaries: We removed

James, It looks like the online NodeJS buildpack is currently pointing to Heroku's repo: http://s3pository.heroku.com/node/... Whereas the offline NodeJS buildpack manifest files seems to be

Hi Lon, The traffic controller takes a subscription ID as a parameter whenever a firehose connection is made. If you use the same subscription ID on each nozzle instance, the firehose will evenly

I'm trying to get an idea of how multiple instances of the firehose-to-syslog app nozzle will interact Does the firehose act like a queue in the sense that once a nozzle reads a message its gone from

Hi all, We recently released nodejs-buildpack v1.5.1 <https://github.com/cloudfoundry/nodejs-buildpack/releases/tag/v1.5.1> which introduces support for Node.js 4.2.2. The full history of

Ok, i got it. I start with 197, but i think you can just verify the iptables of the warden container -- Regards, Yitao jiangyt.github.io

HI Yitao Thank you for your reply. since my cf-release version is 170, I checked and found it has not introduced the security groups concept for this CF version. 2015-11-07 17:04 GMT+08:00 Yitao

Generic UDP routing is kind of hard for multi packet protocols (like SIP or CoAP), you want to make sure packets belonging to same message are routed to same instance of your app. There are two ways

Thank you for the response, Shannon, Great! I will read them. Thanks. -- Noburou TANIGUCHI shannon wrote ----- I'm not a ... noburou taniguchi -- View this message in context:

Just figured out that I could do it by reading out the application environments, but this will be quite messy and I'm not sure if this will work properly. So if there is an easier way, I'd appreciate

Sorry for not being clear enough. Well I am trying to get the relations from the CloudFoundryClient in Java to see which services belong to a space and which spaces are in an organization. I can

you need some way to get the service binding details from you app into the config service (Zookeeper, or SCC). i suppose you could have something do it on a cron schedule or something. your app also