Trigger Feed vs Non-Feed inputs apply differently

I've run into the following issue trying to deploy triggers/rules to IBM Cloud Functions.

Trigger inputs seem to have different behaviour depending on whether or not a `feed` parameter is specified. Without a feed parameter, the inputs array is sent as an object to the Parameters object in Functions, which is then passed to triggered actions as part of the input payload. When given a feed parameter, in this case `/whisk.system/alarms/alarm`, the expected feed parameters work (`cron`, `timezone`) and correctly configure the trigger, but any additional parameters aren't passed to the Parameters object as above.

The `trigger_payload` parameter seems like it would be the way to go in this case, but when setting it as documented (see below screenshot of the created trigger's spec from a GET) it does seem to apply but isn't passed along to the actions as is the case with the Parameters object.

Is there a different syntax I should be using for the `payload` value?

Alternatively, is there a way to define a separate set of inputs that will be parsed differently so I can populate both the feed inputs and the Parameters object?

I've attached the manifest and deployment files below (as txt due to GH restrictions).

Note that using typed bindings for parameters in the manifest doesn't seem to make a difference.

[deployment.txt](https://github.com/apache/openwhisk-wskdeploy/files/3751479/deployment.txt)
[manifest.txt](https://github.com/apache/openwhisk-wskdeploy/files/3751480/manifest.txt)

@mrutkows