Thanks for the clarification Iryna! I'll do some more studying and respond if I have further questions. Mike

Hey Mike, We expect no app routability or log availability downtime during the 3 step CA/cert rotation. That is because during Step 1 we make all components trust both CAs - the old one and the new

Thanks for the heads up David. I have questions about the rotation process. Although all applications may remain up while re-deploying I imagine things like loggregator will stop working mid deploy

Hello Carlo, I'm definitely interested by your step that checks if any of the certs are close to the expiration date! If you can share this on a Github somewhere it would be perfect! Cdt,/Benjamin

I refer to the first proposal since the second option (re-start the instance) would clear all applications from the cache and not only the one that was deleted from persistency. It will lead to

Just a couple of random notes about this: - since we have a lot of certificates in our deployment manifest (not just the CF/diego ones) we actually have a step in our deployment process that

> Was the current maximum number of instances really implemented?. No, it wasn't implemented yet. But it's just an improvement to avoid calling the API. > I see your point however it sounds like

Hi Carlo, Was the current maximum number of instances really implemented?. I see your point however it sounds like something that should be provided centrally. Do you consider this as

Sergio, there are multiple ways to do this: - call the API to get the number of instances and then send the request to each instance, making sure that each instance confirms that the cache was

Thanks Zach and team for sharing. Looking forward to the details during next call and super happy to consider a broker for a Windows Service. I believe this would be a first! Hopefully not

Hi All, There's a SQL Server service broker currently in the incubator, but it appears to be abandoned. We'd like to propose replacing it with this newer broker built by Jared Gordon and Mallika Iyer

Hi Chris, I know this API. I don’t think it is suitable for productive scenarios since it might break if an instance was added/removed while creating the requests. I was looking for some

Hi Sergio, Take a look at the "X-CF-APP-INSTANCE" header: https://docs.cloudfoundry.org/devguide/deploy-apps/routes-domains.html#surgical-routing -Chris

Hi cf-dev, In one of our projects we use an NGINX based application that uses NGINX cache capabilities. We store in cache static file content that belong to a UI application. From time to time we

Hey cf-dev, The Release Integration team has had a few reports from other CF engineering teams that their long-running environments have had their internal TLS certificates expire. Since certificates

Carlo, Just saw this feedback. Thank you very much for your response. Best, Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.

Really great question, and this is a perfectly reasonable place to ask. We do not have a published list, but generally use the same list as the Apache Software Foundation. They are kind enough to

+1 to Eric's view also. I like being able to (sort of) filter version tags. Thanks,

You can try /Groups?count=100&startIndex=101 to get the next 100. If you want more than 100 in 1 page, you can specify /Groups?count=400&startIndex=1 -- http://www.twitter.com/sivabalans

We also tag out bosh-openstack-cpi and bosh with a 'v' prefix. Here's what the github "draft a new release page" has to say about this > Tagging suggestions > It’s common practice to prefix your