|| at Jun 2, 2013 at 3:42 pm
My old API site is still available here: http://apidocs.cloudfoundry.com/
It hasn't been updated in a little over a year though... on v1, some things
had changed with starting an app to move away from the help request
followed by start call. And I don't know if the messages have changed with
V2... my guess is it includes more metadata now. It doesn't look like I'd
gotten to documenting the DEA though.
I used to simply run "nats sub '>'" to get anything and everything.
Sometimes I'd filter stuff with a "grep -v" for component
From how things used to work, the CC was never concerned with whether or
not the app actually started. That was the responsibility of the Health
Manager. When the start process finished (either success or failure), the
DEA would send a heartbeat containing just that app to the HM. It would
On Sunday, June 2, 2013 3:55:47 AM UTC-7, Gandalf Corvotempesta wrote:
Reading the source and the specs and watching on the bus are the best
ways to figure it out. The format of the messages isn't set in stone, it
occasionally has to change to accomodate new features.
Also, nats-sub is good but [nats-sub-pp](https://github.com/mmb/nats_sub_pp)
I'll try to read the source but what I would like to know is how the
caller will be notified about the receiver response.
For example, if CCNG ask DEAs for a deploy through NATS, how CCNG will be
able to get the DEA response? Are there any "response" event triggered by
DEA and subscribed by CCNG ?