Dev focused conversations, questions and discussions around PRs, etc should happen here.
Quick newbie question:
According to docs, settings are global for the trigger, and handler settings are per instance.
I tried the REST trigger using the Web UI and I was prompted for a port number in both flows. I tried entering both values, and it looks like the compiled app was starting 2 separate servers that wanted to bind to the same address.
Am I missing something?
Ok, I just figured it out.
I shouldn't be pressing on "New action" at the top. I need to hover over the existing flow and another "New action" button appears that re-uses the same instance of the REST trigger.
👍
¿?
is there one?
Hi @mellistibco, graphql schema parsing error observed for graphql trigger - opened an issue project-flogo/graphql#10.
Just wanted to confirm. flogo-web is now Open sourced (BSD3) correct? I found the LICENSE file committed April 1st by @mellistibco, but just wanted to make sure. My company had earlier passed on flogo as a UI enabled code publishing solution. I believe the exact words from one of my fellow developers was "It's Awesome but not Open Source Awesome"
Pretty awesome to hear you’re looking to use Flogo! Let us know if there is anything we can do to help
Hello @skothari-tibco , and thank you for your support. With the new mqtt-trigger/mttq-activity we have solved our bottleneck with Rabbit, where the old mqtt-activity were opening/closing an MQTT client for every call. Just to better understand how the new activity works, i've seen in the source code that there's not a "close" on the client. How the opening/closing is managed?
Hello @skothari-tibco , we are experiencing some difficult with the mqtt-activity. We have mapped in the settings the topic like this "/foo/:a" and in map inputs, topicParams is
{ "a": "{{$activity[myactivity].mytopic}}"}
mytopic is an output string from a our custom activity. Now we are receiving the mqtt message but the topic on we receive it is: "/foo/{{$activity[myactivity].mytopic}}". We were expecting that we'll receive the mqtt on "/foo/mytopic". What are we wrong?
{ "a": "{{$activity[myactivity].mytopic}}"}
mytopic is an output string from a our custom activity. Now we are receiving the mqtt message but the topic on we receive it is: "/foo/{{$activity[myactivity].mytopic}}". We were expecting that we'll receive the mqtt on "/foo/mytopic". What are we wrong?
Dear @skothari-tibco , just a little help more. How can I get the param 0 of the topic? I've configured my trigger to receive on /foo/# but I can't access to the # with $flow.topicParams["0"] or $flow.topicParams[0]. I've tried configuring the trigger with the topic /foo/#param1 but it crash..