Hi Nils, I cannot seem to reproduce this. I am logged in as an org-manager: $ cf services Getting services in org ncalugar-a1 / space ncalugar-a1 as ncalugar+a1-org-manager(a)pivotal.io... OK name ser

Before confirming the new version of fog fixed this, I tried to reproduce the error using CF v233. Instead of reproducing the error, it actually worked. V2 CONFIG: provider: 'OpenStack' openstack_tena

Hi Rich, We investigated and determined the recursive chown was not necessary. The commit is still working it's way through CI, but will hopefully make it in the next CF-Release: https://www.pivotaltr

We are adding STAGING_STARTED and STAGING_STOPPED app usage events: https://www.pivotaltracker.com/story/show/111168816 We've also blocked staging an app's package if the app has a package that is sta

Hi Piotr, You are correct, the next start would simply contain the new buildpack used to stage the droplet. Thanks for the feedback on the new event, as long as everyone is ok with DROPLET_CHANGED, I'

Hi Matthew, Thanks for the response. When we start an app in V3, we will always know the buildpack because we are starting the app's current droplet. The droplet was staged with a particular buildpack

Hi Hristo, I'm fine with a PR to add these two fields. Would it make sense to add previous state as well? Thanks, Nick

Hi CF-Dev, We are continuing work on the Cloud Controller V3 API and had a question about a particular App Usage Event we write as part of V2, the BUILDPACK_SET event. The test[1] around this indicate

We have a story in flight: https://www.pivotaltracker.com/story/show/115793253 If upgrading fog doesn't work, we'll happily take a PR that resolves this. wrote:

Hi Muhammad, Unfortunately, we don't have an environment using keystone v3. We are passing the configuration to fog as-is. There are several fixes that have been made in later releases of fog, for exa

Hi Rafal, Packages are not stored in the database for the V2 API, that table is for experimental V3 support and wouldn't have any rows unless you are pushing apps with the V3 API. Can you tell us how

Hi Pradma, Sorry for the delayed response. You've accurately characterized the current behavior. One additional item to note is the error message accurately reflects which quota is not allowing new re

Hi Ponraj, I don't think the CC can make any determination regarding the validity of environment variables as the CC doesn't (and shouldn't) know how each buildpack will use these environment variable

Hi Siva, 1. If you run the PostgreSQL, you likely want to temporarily open the firewall to load data or get on a jump box of some sort that can access the database. It's not really a CF issue at this

Hi Siva, You'll have to tell us more about how your PostgreSQL and CF was deployed, but you might be able to connect to it from your local machine using the psql CLI and the credentials for one of you

Hi Juan Antonio, Support for PWS is available here: http://support.run.pivotal.io/home Is your application a worker (one that doesn't respond to http)? If so, you should disable the health check per h

Hi Matthew, You could use something like Zend\Mail and the Zend\Mail\Transport\Smtp, an SMTP implementation in PHP. http://framework.zend.com/manual/current/en/modules/zend.mail.introduction.html http

Hi Sree, Not sure if this is possible, but maybe instead of requireAtLeastOneSpecialCharacter boolean, you could do minSpecialCharacters int (0-n)? This would allow more rigorous password policies. Ni

Hey Guillaume, To be fair, this did take some time to figure out on our end. It has to do with the interaction between BOSH and Monit. As Dieu mentioned, runtime has a story to potentially determine a