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. See

You might try moving the nameserver entry for the consul_agent in /etc/resolv.conf on the cloud controller to the end to see if that helps. -Dieu

Hi Mike, Yes, moving gets stickier very quickly and precisely what one team wants to have preserved across an org may differ depending on use case. Service bindings, environment variables, routes, mem

Hi Guillaume, We could consider exposing on a droplet [1] the additional metadata that you've mentioned, such as the buildpack guid for a system buildpack or the git sha given a buildpack url. I think

The default org quota you're seeing is defined here [1] I believe you can configure it by specifying the name of the quota you would like to have as the default quota in your manifest. For example: pr

You can call this end point to retrieve the org memory usage http://apidocs.cloudfoundry.org/222/organizations/retrieving_organization_memory_usage.html You would then need to check this against the o

I'm curious if region is perhaps too specific? Perhaps some other generic word would be better so that it's not prescriptive. -Dieu jsdelfino(a)gmail.com> wrote:

Yes, we plan to fully remove support for v1 service brokers at the end of the year.

Have you tried using the nested end point? http://apidocs.cloudfoundry.org/221/apps/list_all_service_bindings_for_the_app.html -Dieu CF CAPI PM bren(a)juanantonio.info> wrote:

Hi Steffen, Cool stuff. It's good to see there's some improvement under jruby. Would be interested to see how this performs on aws or on soft layer. Also, were you able to run CATS? Or is more work ne

On further review, there's a mix of return codes currently returned on deletion. Some end points that return 204's on delete(apps, buildpacks, spaces, orgs) Some end points that return 201 (remove a r

Hi All, Most of cloud controller api's v2 end points currently return a 201 on delete. I would like to get feedback on how the community would feel if we change this to return a 204 No Content. In som

I'll look into getting that page updated. One known issue is that CC doesn't have a concept of a default shared domain when pushing apps. The CLI assumes it's the first shared domain that comes back i

We generally recommend to use a separate system domain from the shared apps domain. That could look like Our test environment for example uses a1.cf-app.com as the system domain and a1-app.cf-app.com

Hello All, Pivotal would like to nominate Steven Benario for the Project Lead on project Greenhouse. Steven is a new hire with experience working for Microsoft on the .NET stack. Steven's experience w

Hello All, Pivotal has asked Erik Jasiak, the current Project Lead for the Logging and Metrics team, to focus on another Pivotal project. Therefore, Pivotal would like to nominate Jim Campbell as the

Hi Jonas, You'll need to escape the special characters like $. See this tracker story for some background: https://www.pivotaltracker.com/story/show/76655240 -Dieu

Thanks Mike. Totally understandable.

Your edge load balancer should be configured to add x-forwarded-for and x-forwarded-proto headers. bren(a)juanantonio.info> wrote:

Separate from this proposal, the CAPI team has stories for spiking on a few different api documentation options for the cloud controller api [1]. Swagger is one of the options we are looking into, but