Add "shim" support to triggers. A trigger with a shim is one that can bypass the regular engine hosting and control how it is invoked. Directly through its own main or as a plugin.
When an app has a trigger with a shim, that shim can be specified to be used in the build step using the trigger id of the trigger with the shim:
flogo build -shim <triggerId>
Shims can be set on a trigger by adding "shim":"main" (specifies its own main) or "shim":"plugin" (indicating that the shim entrypoint is via a go plugin). The trigger should also contain a "shim" directory with its necessary support file.
shim/shim.go <-- for plugin or main
shim/Makefile <-- if plugin type, for now looks for "Makefile" that will be invoked at build time
Add "shim" support to triggers. A trigger with a shim is one that can bypass the regular engine hosting and control how it is invoked. Directly through its own main or as a plugin.
When an app has a trigger with a shim, that shim can be specified to be used in the build step using the trigger id of the trigger with the shim:
flogo build -shim <triggerId>Shims can be set on a trigger by adding "shim":"main" (specifies its own main) or "shim":"plugin" (indicating that the shim entrypoint is via a go plugin). The trigger should also contain a "shim" directory with its necessary support file.