Yueming Xu

Isn't the spec of this package reversed from Jolt? Jolt spec maps from input field to output field path, while kazaam maps output field to input field path. Would this...

I haven't been maintaining this repo. An updated version is at https://github.com/dovetail-lab/fabric-operation, which is also a few months old since I last updated it, although it supports the newer chaincode...

Yes, I would discourage (actually disable) multiple triggers for a same flow. Instead, define subflows that can be reused by multiple flows, but limit one trigger per flow. That is...

Of course it is up for debate regarding the pros-and-cons of different approaches (both achieve the same purpose.) For this issue, however, I hope that the API can expose a...

Actually, all I need is to be able to specify which additional attributes need to be exposed as a flow property in the following call made by my trigger implementation:...

@mellistibco That might work if you do not define any input mapping, although in that case, you won't see any attributes on the Flogo UI, which would be a problem...

--cv is not flexible enough to override other things. For example, I need to build package with shim trigger that requires patches for both flogo/core and flogo/flow versions, as well...

I agree that the nesting of "mapping" does not seem necessary even for inputs. I noticed that the Flogo OSS and Enterprise export/import trigger/activity settings differently. OSS actually handles settings...

Yes, I am compiling Flogo flow as a third-party app (i.e., Hyperledger Fabric v1.4 chaincode), which does not support go module, and so flogo packages are included under vendor folder,...