hazaar/hazaar-warlock
1
0
Fork 0
Code Issues Pull requests 2 Projects Releases 4 Packages Wiki Activity Actions

Global event subscriptions #46

New issue
Closed
opened 2019-04-13 21:53:49 +00:00 by jamie · 6 comments
jamie commented 2019-04-13 21:53:49 +00:00 (Migrated from git.hazaar.io)
Copy link

Now that we can schedule tasks from the main warlock process, I think it would be awesome to be able to start jobs from events as well. So in the main config you can setup an event subscription the same as a scheduled task and when the even occurs a new process is started and sent the event payload as an argument.

Now that we can schedule tasks from the main warlock process, I think it would be awesome to be able to start jobs from events as well. So in the main config you can setup an event subscription the same as a scheduled task and when the even occurs a new process is started and sent the event payload as an argument.
jamie commented 2019-04-13 21:53:49 +00:00 (Migrated from git.hazaar.io)
Copy link

changed milestone to %2

changed milestone to %2
jamie commented 2019-04-14 23:03:44 +00:00 (Migrated from git.hazaar.io)
Copy link

created merge request !18 to address this issue

created merge request !18 to address this issue
jamie commented 2019-04-14 23:03:48 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in merge request !18

mentioned in merge request !18
jamie commented 2019-04-15 07:20:24 +00:00 (Migrated from git.hazaar.io)
Copy link

closed via merge request !18

closed via merge request !18
jamie commented 2019-04-15 07:20:25 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in commit aeee40690f735d24d00c18a58919ac1a771ca703

mentioned in commit aeee40690f735d24d00c18a58919ac1a771ca703
jamie commented 2020-04-14 23:30:32 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in commit 9ccf6fe3dc

mentioned in commit 9ccf6fe3dcfcb012e0b186dd1e3b645039124529
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
3.0-develop
58-restful-triggers
2.2-stable
2-warlock-to-warlock-communication
release-2.2.3
release-2.2.2
release-2.2.1
release-2.2.0
release-2.1.5
release-2.1.4
release-2.1.3
release-2.1.2
release-2.1.1
release-2.1.0
release-2.0.2
release-2.0.1
release-2.0.0
release-1.2.6
release-1.2.5
release-1.2.4
release-1.2.3
release-1.2.2
release-1.2.1
release-1.2.0
release-1.1.9
release-1.1.8
release-1.1.7
release-1.1.6
release-1.1.5
release-1.1.4
release-1.1.3
release-1.1.2
release-1.1.1
release-1.1.0
release-1.0.6
release-1.0.5
release-1.0.4
release-1.0.3
release-1.0.2
release-1.0.1
release-1.0.0
release-0.4.0
release-0.3.0
release-0.2.0
release-0.1.0
Labels
Clear labels   
bug

   
confirmed

   
critical

   
discussion

   
documentation

   
Doing

   
enhancement

   
suggestion

   
support

   
To Do
No labels
bug
confirmed
critical
discussion
documentation
Doing
enhancement
suggestion
support
To Do
Milestone
Clear milestone
No items
No milestone
Version 2.2
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-warlock#46
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?