Dr. Nic created the cloudfoundry-community github org but anyone who is a current member of the org can invite others. I've sent you an invite. Please keep in mind that org is not managed by the Cloud

You might consider making a tiny custom 404 app and then map *.cf.bar.io and *.foo.bar.io and any other sub domains to it so that it doesn't fall through to your landing page app. Would that work for

Hi, The Routing team has the Route Services work in progress [1]. I believe once that work is complete you could develop a route service to be able to do this type of rate limiting. Shannon may be abl

Hi Kinjal, We generally recommend naming it with a specific identifiable folder name that is not the bucket root. This might look like: ... buildpack_directory_key: buildpacks .... droplet_directory_k

Hi Jack, There are not any explicit environment variables that we expose that an app is running on DEAs or on Diego. My best suggestion here would be to set an environment variable explicitly and trig

Sorry, I skimmed over that particular snippet. Based on that description, perhaps then double checking your entry for router.ssl_cert and router.ssl_key and comparing against your existing deployment'

Apologies Mike. It was my understanding that the endpoint was incomplete/non functional and as it was marked experimental, was okay to remove. Dieu CF CAPI PM

Hi James, That sounds like you might be using a self signed cert and CC is failing trying to do cert verification. You can try specifying in your manifest properties.ssl.skip_cert_verify: true https:/

Thanks for the reminder James. For those stemcell changes we had investigated packaging rpc-bind and nfs-common for cloud controller and nfs so that bosh could remove those from the stemcell. [1] I'll

Hi Mike, We could keep the nfs mounting job and the capability for cc to connect to an external non-bosh deployed nfs as an option. We would still like to replace the nfs job with the webdav job as th

Hi Kris, Unused repos typically go to the cloudfoundry-attic. You might consider putting it there instead. -Dieu

Hi All, The CAPI team is working on deprecating usage of nfs for the default blobstore in cf-release in favor of the webdav protocol. I'm interested to know if anyone is using their own separate nfs,

Hi Ponraj, The summary end point is used in many ways but it was intended to give insight into what a user has visibility to. The memory_usage end point was added as a convenience end point and its in

Hi John, We don't currently have a better alternative. I do think such a role would be useful. We're currently very focused on v3, process types, and tasks, however. I'm not entirely sure what would b

Hi All, We've put together a proposal for exposing Tasks. The goal of exposing this feature is to enhance the cloud controller and the cf cli to support the ability for a space developer to create and

Yes, you can use cf curl with the --output parameter to download a droplet. -Dieu CF CAPI PM bren(a)juanantonio.info> wrote:

I believe the cf curl command simply passes the correct authentication headers and the --output option to curl. I don't believe there's any other cli code involved. -Dieu bren(a)juanantonio.info> wrot

For 1. At minimum, you'll need to look at what application security groups apply to your app, and have your admin add a new application security group for that private ip range and bind it to your app

The Context Path Routing work has been completed on the cloud controller API side and work to add support for it in the cf cli I believe is nearly complete. Until then, you could use this context path

The curl examples in the existing api docs aren't great. We hope to improve that in future. You can do this with cf curl fairly easily with the --output flag. For example: $ cf curl /v2/apps/ef01a7da-