Hi all, Several releases, including cf-release and diego-release, use an AWS account belonging to the Cloud Foundry Foundation to store final release blobs. This account was accidentally closed,

If the question can be paraphrased as "when colocating multiple job (templates) on a single VM, will they start in parallel or instead in some sort of order?" then the jobs will generally come online

yes, they are always returned. introducing an option sounds like a good idea for the systems that wish to turn it off, thanks for the

Thanks Filip for your answer. Wouldn't it make sense to progressively change this behavior, possibly controlled by a configuration option to give clients time to handle this incompatible

For option 2 would it not be simpler to have a single property such as cc.blacklisted_system_domain_routes that contains the desired list and have the CC deny route requests for those routes? I don't

The access token used to double down as an identity token before OpenID Connect was standardized, now that we have implemented id_token, we don't really need it. but removing it would cause an

Hi, I wonder the rationale for apparenty uaa-specific [0] user-related fields in the access token (username, email [1]) while they are now returned in a standard maneer in the openidconnect id

Hi Cloud Foundry, We've had a recurring issue brought to our attention regarding a Cloud Foundry deployment using a system_domain that is in the list of app_domains. When the system domain is in the

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

Hi Ryan, Thanks for your e-mail. I'm following the instructions from https://github.com/cloudfoundry-incubator/diego-release This is how I generate my certificates CA certificate $ certstrap init

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'

Hi Ricky, We think there might be an issue with the TLS certs that you provide in the etcd properties of the manifest. Can you tell us how you generated these certs? We also discovered an issue with

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

Wohoo!!!!!!!!

Hi, "execution expired" in most cases means that the registry cannot be reached from the newly created VM. Make sure that your BOSH director is reachable on port 25777 from the new VM. As Gwenn

Hi, There seems to be a difference between how "cf services" and "cf service" are working in regard of permissions and I would like to understand why. As organization manager but without a role in a

Hello Hope you are doing well. I wanted to bring to your attention the latest SNS Research report in which you might be interested, " The M2M, IoT & Wearable Technology Ecosystem: 2015 - 2030 -

Hi Adrian, Thanks for your reply. The log file for the database is too big to be attached by e-mail, so I have uploaded to dropbox. You can access it

Per the thread in here <https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/thread/E4XL4GTTDAPNDDEGE7NASKPMLESRIT3Z/#E4XL4GTTDAPNDDEGE7NASKPMLESRIT3Z> a while back, the varz

Hi Sam, Sorry for the slow response - Monday and Friday were public holidays in the UK (where the Garden team are based) so we didn't get a chance to look in to this. I think your understanding of