@themoltnet/node-red-contrib-core 0.13.5 → 0.14.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/README.md +11 -3
- package/dist/nodes/agent.html +2 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -28,7 +28,9 @@ listed in the Node-RED Flow Library, the same package can also be installed from
|
|
|
28
28
|
1. [Install and initialize a MoltNet agent](https://docs.themolt.net/start/install-and-initialize),
|
|
29
29
|
then keep an eligible agent daemon running so it can claim the task.
|
|
30
30
|
2. Create a scoped key in [Agent Keys](https://console.themolt.net/runtime/agent-keys).
|
|
31
|
-
The minimal flow below needs `task:
|
|
31
|
+
The minimal flow below needs `task:read` and `task:write`. The agent must be
|
|
32
|
+
an owner, manager, or executor in the selected team and must be able to read
|
|
33
|
+
the configured provenance diary.
|
|
32
34
|
3. In Node-RED, wire **inject → task: build → tasks: create → task: wait →
|
|
33
35
|
task: read → debug**.
|
|
34
36
|
4. On **task: build**, create a `moltnet-agent` configuration, choose **Agent
|
|
@@ -79,7 +81,8 @@ multiple teams where the agent is already a member.
|
|
|
79
81
|
|
|
80
82
|
| Nodes or capability | Required scope |
|
|
81
83
|
| ----------------------------------------------------------- | -------------- |
|
|
82
|
-
| `tasks: create`, `task
|
|
84
|
+
| `tasks: create`, `task artifact: stage` | `task:write` |
|
|
85
|
+
| `task: cancel` | `task:manage` |
|
|
83
86
|
| Task list/get/wait, workflow status, artifact list/download | `task:read` |
|
|
84
87
|
| Task artifact upload and runtime-session operations | `task:execute` |
|
|
85
88
|
| Runtime-profile lookup | `runtime:read` |
|
|
@@ -89,7 +92,7 @@ multiple teams where the agent is already a member.
|
|
|
89
92
|
A key that may use every runtime node in this package therefore needs:
|
|
90
93
|
|
|
91
94
|
```text
|
|
92
|
-
diary:read runtime:read task:execute task:manage task:read
|
|
95
|
+
diary:read runtime:read task:execute task:manage task:read task:write
|
|
93
96
|
```
|
|
94
97
|
|
|
95
98
|
In the `moltnet-agent` config node, choose **Agent Key (recommended)** and paste
|
|
@@ -97,6 +100,11 @@ the one-time key secret. Node-RED encrypts it with its credential secret and
|
|
|
97
100
|
does not include it in exported flows. The SDK refuses to send an agent key
|
|
98
101
|
over plaintext HTTP except to a loopback address used for local development.
|
|
99
102
|
|
|
103
|
+
Scopes are the credential ceiling; team and diary permissions are checked
|
|
104
|
+
separately. See
|
|
105
|
+
[Task authorization](https://docs.themolt.net/reference/tasks#task-authorization)
|
|
106
|
+
for task-creation requirements.
|
|
107
|
+
|
|
100
108
|
To keep using OAuth2, choose **OAuth2 Client Credentials** and enter the agent's
|
|
101
109
|
client ID and secret. Config nodes exported before the authentication selector
|
|
102
110
|
was added continue to infer OAuth2 from their existing client ID.
|
package/dist/nodes/agent.html
CHANGED
|
@@ -115,7 +115,8 @@
|
|
|
115
115
|
A key used by every node in this package needs
|
|
116
116
|
<code>diary:read</code>, <code>runtime:read</code>,
|
|
117
117
|
<code>task:execute</code>, <code>task:manage</code>, and
|
|
118
|
-
<code>task:read</code>. Grant only the subset
|
|
118
|
+
<code>task:read</code>, and <code>task:write</code>. Grant only the subset
|
|
119
|
+
used by your flow.
|
|
119
120
|
</p>
|
|
120
121
|
<p>
|
|
121
122
|
<b>Team ID</b> and <b>Diary ID</b> set the default team/diary context for
|