@requence/task 0.8.5-edge.1242 → 0.9.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +25 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,30 @@
|
|
|
1
1
|
# @requence/task
|
|
2
2
|
|
|
3
|
+
## 0.9.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- 1b79f3e: Automations can be managed with an access token.
|
|
8
|
+
|
|
9
|
+
An outside application can now create, read, start, stop and delete an
|
|
10
|
+
automation without a session, at `/api/automation`. Both SDKs have functions for
|
|
11
|
+
it: `createAutomation`, `getAutomation`, `startAutomation`, `stopAutomation` and
|
|
12
|
+
`deleteAutomation` in `@requence/task`, and `create_automation`, … in
|
|
13
|
+
`requence.task`.
|
|
14
|
+
|
|
15
|
+
Create takes an optional `id`. Mint a new random uuid, save it in your own store
|
|
16
|
+
first, then create with it: a retried create gets `AUTOMATION_EXISTS`
|
|
17
|
+
(`AutomationExistsError` / `AutomationExistsException`), so it can never make a
|
|
18
|
+
second automation. The id of a deleted automation gets `AUTOMATION_DELETED` and
|
|
19
|
+
can never be used again.
|
|
20
|
+
|
|
21
|
+
Create and update now refuse an automation that cannot run: a template that is
|
|
22
|
+
missing, disabled, has errors or has the wrong role, a trigger without exactly
|
|
23
|
+
one exit node, and an action that cannot take what the trigger yields (with or
|
|
24
|
+
without a mapping function). Before, such an automation was saved, showed
|
|
25
|
+
**Running**, and did nothing. The wizard makes the same check; when the typing
|
|
26
|
+
service is not reachable, saving fails with a message to try again later.
|
|
27
|
+
|
|
3
28
|
## 0.8.4
|
|
4
29
|
|
|
5
30
|
### Patch Changes
|