@sjawhar/pi-envoy 17.29.2 → 17.30.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/dist/envoy.js +1 -1
- package/dist/skills/agent-secrets/SKILL.md +20 -3
- package/package.json +1 -1
package/dist/envoy.js
CHANGED
|
@@ -47651,7 +47651,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
|
|
|
47651
47651
|
|
|
47652
47652
|
// package.json
|
|
47653
47653
|
var name = "@sjawhar/pi-envoy";
|
|
47654
|
-
var version2 = "17.
|
|
47654
|
+
var version2 = "17.30.0";
|
|
47655
47655
|
var package_default = {
|
|
47656
47656
|
name,
|
|
47657
47657
|
version: version2,
|
|
@@ -29,10 +29,27 @@ agent-secrets NAME... [--reason TEXT] [--wait DURATION] [--ttl DURATION] -- <com
|
|
|
29
29
|
`--github-token`, the secret's name holds that one account's token, the string an
|
|
30
30
|
`Authorization` header carries. Without `--github-token` the name holds the JSON object of
|
|
31
31
|
installations, and a command that sends that object to GitHub reads `401`.
|
|
32
|
+
- The broker checks a narrowing before the approval request, so a narrowing it cannot serve costs
|
|
33
|
+
nobody an approval. It refuses the request, nothing runs, and the status is 1, in five cases:
|
|
34
|
+
|
|
35
|
+
- an account the secret's `github-owners` tag does not list,
|
|
36
|
+
- a run that names no GitHub App secret,
|
|
37
|
+
- a name behind the airlock (the bullet below),
|
|
38
|
+
- a narrowing GitHub itself refuses, such as a repository the App's installation does not
|
|
39
|
+
reach, or read access the App does not hold,
|
|
40
|
+
- an account the App is not installed on, which the message says in the words `has no
|
|
41
|
+
installation on`. Install the App on that account, or narrow to an account it is on.
|
|
42
|
+
|
|
43
|
+
The message says which of the five it is. Two cases keep the older behaviour, where the
|
|
44
|
+
refusal comes when the grant is read instead: a request every name of which is granted at
|
|
45
|
+
once, which no person decides, and a request on which the broker reaches no verdict, for
|
|
46
|
+
example because GitHub is out of reach or refuses the App itself, or because the check passes
|
|
47
|
+
its own time bounds.
|
|
32
48
|
- A narrowing and the airlock do not go together. Ask for a narrowing in a run whose grant holds
|
|
33
|
-
a secret behind the airlock (below) and
|
|
34
|
-
|
|
35
|
-
|
|
49
|
+
a secret behind the airlock (below) and nothing runs: where a person decides the request,
|
|
50
|
+
the broker refuses the request, naming that secret, and where the policy grants every name
|
|
51
|
+
at once, the same refusal comes when the grant is read. Ask for the GitHub App secret in a
|
|
52
|
+
run of its own, with no airlocked name beside it.
|
|
36
53
|
|
|
37
54
|
## The command reads the value, your shell does not
|
|
38
55
|
|