turbot / flowpipe

Flowpipe is a cloud scripting engine. Automation and workflow to connect your clouds to the people, systems and data that matters.
https://flowpipe.io
GNU Affero General Public License v3.0
353 stars 13 forks source link

Add ability to run a trigger from a `flowpipe` command #740

Open cbruno10 opened 6 months ago

cbruno10 commented 6 months ago

Is your feature request related to a problem? Please describe. When testing a trigger, if my schedule has a long interval, I need to wait a while until it triggers

Describe the solution you'd like Add the ability to run a trigger immediately

Describe alternatives you've considered Reduce the interval for testing

Additional context Add any other context or screenshots about the feature request here.

judell commented 6 months ago

The other alternative we have used, and shown in the demo, is a query step.

On Thu, Feb 29, 2024 at 11:48 AM cbruno10 @.***> wrote:

Is your feature request related to a problem? Please describe. When testing a trigger, if my schedule has a long interval, I need to wait a while until it triggers

Describe the solution you'd like Add the ability to run a trigger immediately

Describe alternatives you've considered Reduce the interval for testing

Additional context Add any other context or screenshots about the feature request here.

— Reply to this email directly, view it on GitHub https://github.com/turbot/flowpipe/issues/740, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALLLMB7BBM3CRIQGML54TYV6CYVAVCNFSM6AAAAABEARRDLSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3DCOJYGQ3TEMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

e-gineer commented 6 months ago

Proposed format for this command is:

flowpipe trigger run my_trigger

For http triggers that require a payload / data, the format should be similar to curl:

flowpipe trigger run my_trigger --data '{ "foo": "bar" }'

After being run, the output of the command would match the flowpipe pipeline run command.

github-actions[bot] commented 4 months ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

github-actions[bot] commented 3 months ago

This issue was closed because it has been stalled for 90 days with no activity.