Once - configurable on a per-app, per space, or per deployment basis? -- -- Matt

For me the primary use case to developing management tools on top of the CC API, and being able to intelligently cache information about the state of those resources. Without etags or serial numbers

Hi All, I wrote a couple of articles about droplets and stacks. http://www.cloudcredo.com/a-droplet-of-value/ http://www.cloudcredo.com/stacks-of-problems/ The droplet post is fairly

Hey all, Based on the feedback we got and the relatively low cost to maintain privileged support we'd like to propose making running privileged containers on the platform configurable - we will

Now I see what that means. Each line of a multiline log message could be sent to a different logstash server. Definitely problematic. Especially with the ephemeral nature of the CF logs there needs to

fails, as exp reads 1438228276 most likely your client does not have the access token validity setup correctly. See the test case I posted that validates my

Good. But my apologies. Assume: creation time = 1438184877 access token validity (set by me) = 315360000 exp is expected to be 1753544877 when decoded. Unfortunately, this test fails, as exp reads

For us the main use case is security auditing to keep a long term record of who has done anything. In the case of our Security team rather than use CF events directly they preferred to have events

Thanks Steve. Though I'm no logstash expert I assume this won't work if you have multiple logstash machine's doing filtering like Simon mentioned right? Same is true for us with splunk if you are

when decoded to read exp: 315569260. If this is not, then is it possible to set the token expiry time? It's a little bit different. access_token_validity is how long the token is valid for from the

Thanks again Filip. However, here's what I mean, If I set the access_token_validity to 315569260, I'm expecting the token when decoded to read exp: 315569260. If this is not, then is it possible

Here's a suggested pattern to handle stack traces. http://stackoverflow.com/questions/31657863/logstash-and-multiline-log-entry-from-cloud-foundry?noredirect=1#comment51279061_31657863

Hi Sai, Thanks for asking these questions. The buildpacks team, who currently maintains the nodejs-buildpack, is totally open to improving the node.js developer experience. I'd love to hear about

Hey All, I've recently started investigating a memory issue with Node.js apps running in CloudFoundry environments. FYI, I'm using CFv210. As an example, if I push a Node.js app with a mem leak

I don't think the schemas belong there, that may be a copy paste error in the docs. The easiest reference for the REST API may be the integration

Token validity is how long a token is valid for from the time it is created. The token will store the expiration time, that is the date when the token expires. so `"exp":1438209609` is actually the

Filip, Even when I set the value to 315569260 (this value seems to be lesser than today though), when I decode the issued token, I get something like this `"exp":1438209609`. Is token validity and

The uaac is much useful for ops use case. However, my use case leans more towards the REST API. Do you an idea why I might be getting those errors. As you can see, the token has got the right

I installed it a while ago and I got some hairy errors. So I just dumped it. I'll try it again. Thanks for mentioning. wrote:

curl -v -H "Authorization: