You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The output of the shim builds of a trigger varies depending on the implementation of the trigger. Because of that the Web UI cannot provide proper support for it as it doesn't know where to look for the file to download.
For example the CLI trigger saves its output to bin/${app-name} but the AWS lambda trigger saves it output to bin/handler.zip (until recently it was src/handler.zip).
Expected behavior:
The trigger's descriptor.json can declare a field like:
{
"shimOutput": "bin/handlers.zip"
}
Which the UI can use to find the output file.
What is the motivation / use case for changing the behavior?
Supporting shim builds in Flogo Web UI
The text was updated successfully, but these errors were encountered:
Current behavior:
The output of the shim builds of a trigger varies depending on the implementation of the trigger. Because of that the Web UI cannot provide proper support for it as it doesn't know where to look for the file to download.
For example the CLI trigger saves its output to
bin/${app-name}
but the AWS lambda trigger saves it output tobin/handler.zip
(until recently it wassrc/handler.zip
).Expected behavior:
The trigger's
descriptor.json
can declare a field like:Which the UI can use to find the output file.
What is the motivation / use case for changing the behavior?
Supporting shim builds in Flogo Web UI
The text was updated successfully, but these errors were encountered: