Mark Deuser

I'm a little confused regarding the issue title and the description. I'm guessing the intent to define some specific default behaviors in the .wskprops configuration file such that these values...

and should probably pass along a message that indicates the trigger was not really fired.. - no rule associate with trigger - no action associated with trigger's rule (need to...

@csantanapr - isn't the `trigger_payload` unique to the alarms trigger feed actions? i agree that these seem to be a functional duplication of trigger parameters

should this be driven by the backend since it knows exactly what runtimes it supports?

sounds good. client would - fetch the backend runtime support whenever the target openwhisk host changes. client would need to manage a local copy of this information for all other...

this appears to be a breaking change as it is currently implemented. if so, i'm not in favor of this change as implemented. one possible implementation is to use an...

`WSK_CLI_PROMPT_ON_CHANGE` and/or `WSK_CLI_PROMPT` do not exist in the backend

@rabbah - is this example still a valid reflection of the updates > `GET /namespaces/_/activations?count=true` return `{"activations": N}`

@csantanapr - yeah, still a nice-to-have

or update the backend to include the status value with the other rule definition data being returned as part of the `wsk rule list` backend api invocation. this would avoid...