Hi expert,my env:cf 213 vsphere 5.5 After redeploy CF in a new environment,  testing spring-music as the first app. When run cf push, get below issue:------------------------------------ $ cf

Hello CF Community, Apologies for the lapse in sending timely Utilities PMC notes (see comments below). These notes are permanently available

After the fix, having override: true should not revoke the tokens. If it still does, then it's a bug and we would like to know. thanks

Awesome. option 2 is definitely the cause of the problem. Thank you very much.

Hello CF community, Apologies for the lapse in sending timely Buildpacks PMC notes (see comments below). These notes are permanently available

We introduced a feature called 'revokable tokens'. A token would automatically be revoked if a client changed it's secret. All tokens issued previously would be automatically revoked. In earlier

Hi, What could cause a valid token to become invalid on UAA restart? I've noticed this overtime, that a token (of client_credentials grant type) which has a validity of 315360000 and has been used

Hi Amit, Sorry, you right. In fact, I'm an user of the CF' Ramon installation ;) Daniel has solve my problems with the last link (JAVA_OPTS

Thanks Matthew. Very detail reply. :) It seems the all-in-one release won't come out soon.

Hi James, Yes, you have reason, I returned to test: https://nodejsssl.MY_IP.xip.io/ and I see the sreeen where Chrome advise the user about a NET::ERR_CERT_AUTHORITY_INVALID so, the node

Yes, there are some differences in the approach from that document. -Dieu

Hi Guillaume, Just to ensure that it will be addressed, could you add it as github issues on the repo? Hoping to do another pass at the remaining open issues later this week. -Dieu

Thanks a lot Matthew and Amit, the document can now be publicly accessed/commented. Guillaume.

Hi all, I will not be able to attend the CAB meeting tomorrow, but I have added my notes to the agenda doc. MEGA has been/will be working on a bunch of exciting things, and I welcome

We're happy to see it. Thanks a lot, Warren. Warren Fernandes wrote ----- I'm not a ... noburou taniguchi -- View this message in context:

Hi all, Ramon, Fabien, are you both working on the same problem or is Fabien's response to Daniel separate from Ramon's original question? I couldn't understand Fabien's response. Did Daniel's help

Agree with Zach, that for the CAPI team we would prefer to just wait for the routing-api to be ready before prioritizing work to change the way CC registers its routes. Dieu

Hello All, I have a resource pool , let say small_z1 - name: small_z1 network: cf1 stemcell: stemcell-xyz cloud_properties: instance_type: m1.small

Hi Michael, What do you consider "large"? In principle, nothing is stopping you from deploying a large cf deployment to your own OpenStack environment. When you say "seeing a large install version

Hey all, The router already has some health check behaviour -- you can naively register routes with it and it's smart about knowing whether to actually route traffic or not. I'd like to understand