@sjawhar/pi-envoy 17.30.2 → 17.30.4
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/dist/envoy.js
CHANGED
|
@@ -47694,7 +47694,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
|
|
|
47694
47694
|
|
|
47695
47695
|
// package.json
|
|
47696
47696
|
var name = "@sjawhar/pi-envoy";
|
|
47697
|
-
var version2 = "17.30.
|
|
47697
|
+
var version2 = "17.30.4";
|
|
47698
47698
|
var package_default = {
|
|
47699
47699
|
name,
|
|
47700
47700
|
version: version2,
|
|
@@ -211,10 +211,11 @@ prompt, a skill, or the issue you work on. There is no list to browse and nothin
|
|
|
211
211
|
secret exists is recorded against your session with the reason you signed, and it reaches a
|
|
212
212
|
person's Inbox unless the model judge decides it first.
|
|
213
213
|
- `UNKNOWN_SECRET` and a denial are final. Do not ask again, and do not try a name of your own.
|
|
214
|
-
- A secret that a service owns
|
|
215
|
-
|
|
216
|
-
|
|
217
|
-
|
|
214
|
+
- A secret that a service owns goes to that service's own pods and VMs and to nothing else:
|
|
215
|
+
`Evaluate` in `packages/envoy/internal/broker/policy/policy.go` grants a service-owned secret at
|
|
216
|
+
once when the session's own service is the secret's owner, and denies every other session, with
|
|
217
|
+
no person asked. A shared agent secret, such as `LEGION_SLACK_BOT_TOKEN`, goes at once to every
|
|
218
|
+
session, a pod's and a person's alike.
|
|
218
219
|
- The `agent-secrets secret` forms (`list`, `show`, `create`, `set`, `retag`, `delete`, `restore`)
|
|
219
220
|
call the broker's store under whatever cloud credential the environment gives them, and the
|
|
220
221
|
store's IAM decides what each may read and write.
|
|
@@ -271,9 +272,8 @@ messages of the thread. A `ts` that names no message answers
|
|
|
271
272
|
`{"ok":false,"error":"thread_not_found"}`, also at exit 0, which is why the body decides and not the
|
|
272
273
|
status. A thread read needs the app's `channels:history` scope in a public channel and
|
|
273
274
|
`groups:history` in a private one; without them Slack answers `missing_scope`, which only a person
|
|
274
|
-
in the Slack workspace can fix.
|
|
275
|
-
|
|
276
|
-
broker identity exits 2.
|
|
275
|
+
in the Slack workspace can fix. `LEGION_SLACK_BOT_TOKEN` is a shared agent secret, so every session
|
|
276
|
+
with a broker identity is granted it; a session with no broker identity exits 2.
|
|
277
277
|
|
|
278
278
|
Paging: Slack recommends a `limit` of at most 200. While the answer's `has_more` is true, pass its
|
|
279
279
|
`response_metadata.next_cursor` as `cursor` to the next call. Each page repeats the thread's root
|