the collections example [1] does not actually include the required *resources* field [1] https://github.com/cloudfoundry/cc-api-v3-style-guide#example-2 -- Thank you, James Bayer

The CF CLI team just cut 6.12.3. Release notes and binaries are available at: https://github.com/cloudfoundry/cli/releases Highlights of this release include: Bug Fix: runtime error: index out

should the PUT example that updates the app name and space guid actually be a PATCH since it updates the resource? https://github.com/cloudfoundry/cc-api-v3-style-guide#put -- Thank you, James

Dan is correct - "cf file" for getting stdout/stderr files directly was deprecated some time ago. I'll try to locate when that happened (it was before my time.) From the cli, "cf logs" for

Have you tried running `cf logs` instead? Anything written to STDOUT or STDERR should be visible there for some period of time. For long term storage, you should look at setting up a log drain on

Hi, we are also facing the same issue when we check the "cf files pfh-cos-dicomobjectstore-dev /logs" we are able to see only the staging logs and not the stdout.log abd stderror.log. we need to

Hi , We are having the same problem where we are not able to see the stdout.log and stderror.log for all the application deployed in the cloud. Could you please let me know how do we access the logs

Hi all, The CF docs for deploying CF to an AWS VPC <https://docs.cloudfoundry.org/deploying/ec2/bootstrap-aws-vpc.html> have a broken link to a Gist of Dan Highham's, that presumably talks

Thanks Dieu for your response. We have successfully implemented an async service broker for out internal dbaas [1], [2] which db farms provisionning sometimes takes longer than 30s. Concerning

Hi All, The CAPI team has created a style guide for v3 of the cloud controller api and would like to share this again with the wider cf community for feedback after initial review within the team.

Thanks Joseph for your response. Any chance that the OSS build pipeline would update the spiff template with the current version number of the cf release being built, as to avoid each consummers of

You can refer to this discussion for some understanding of what is stored in the cc-resources container: https://groups.google.com/a/cloudfoundry.org/forum/#!topic/vcap-dev/nTQSn8spBPE It's

Responses inline. Yes. This isn't a diego thing, this is a CC thing. You likely need to restage the application for ENV var changes to take effect. Unless I'm mistaken, this too is not

Thank you. The pointer to the code is excellent. I was looking in the right place. An odd part was I actually added the CA to the machine itself and it still did not work. I finally opted for a

What is the default memory size of an app deployed in diego? cf apps indicate 1GB. cf set-env doesn't appear to be getting the environment variable information to the running container. Is cf set-env

Hi, I am using Swift as Cloud Foundry blobstore. I noticed there are four containers: cc-buildpacks cc-droplets cc-packages cc-resources For the first three containers, I can find the relationship

great questions, dwayne. 1) the partition key is intended to be used in a similar manner to partitioners in distributed systems like cassandra or kafka. the specific behavior i would like to make

Hi Ben, I was wondering if you could give a concrete use case for the partition key functionality. In particular I am interested in how we solve multi line log entries. I think it would be better to

Unfortunately those properties don't actually do what they say. A story has been added to the CAPI backlog to clean those up, and possibly change

hello!