@sjawhar/pi-envoy 17.18.1 → 17.18.2
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 +11 -5
- package/package.json +1 -1
package/dist/envoy.js
CHANGED
|
@@ -46663,7 +46663,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
|
|
|
46663
46663
|
|
|
46664
46664
|
// package.json
|
|
46665
46665
|
var name = "@sjawhar/pi-envoy";
|
|
46666
|
-
var version2 = "17.18.
|
|
46666
|
+
var version2 = "17.18.2";
|
|
46667
46667
|
var package_default = {
|
|
46668
46668
|
name,
|
|
46669
46669
|
version: version2,
|
|
@@ -199,7 +199,8 @@ prompt, a skill, or the issue you work on. There is no list to browse and nothin
|
|
|
199
199
|
grants a service-owned secret at once when the session's own service is the secret's owner, and
|
|
200
200
|
denies every other session, with no person asked.
|
|
201
201
|
- The `agent-secrets secret` forms (`list`, `show`, `create`, `set`, `retag`, `delete`, `restore`)
|
|
202
|
-
|
|
202
|
+
call the broker's store under whatever cloud credential the environment gives them, and the
|
|
203
|
+
store's IAM decides what each may read and write.
|
|
203
204
|
- Slack's read methods go through `curl` under this client. Every post to Slack stays a `slack_post`
|
|
204
205
|
call, which holds the reply to one thread, to 4,000 characters and to one send.
|
|
205
206
|
|
|
@@ -223,12 +224,17 @@ for two reasons:
|
|
|
223
224
|
`agent-secrets register --wait 10 --exec -- <the agent's command>`.
|
|
224
225
|
|
|
225
226
|
On `UNKNOWN_SECRET` you stop, as above. You may tell the secret's owner how to find the cause:
|
|
226
|
-
`agent-secrets secret list` and `agent-secrets secret show NAME`, under
|
|
227
|
-
(`gcloud auth login` against a broker on Google Cloud,
|
|
227
|
+
`agent-secrets secret list` and `agent-secrets secret show NAME`, under a cloud sign-in that may
|
|
228
|
+
read the store (`gcloud auth login` against a broker on Google Cloud, an `AWS_PROFILE` against one
|
|
229
|
+
on AWS).
|
|
228
230
|
|
|
229
|
-
|
|
231
|
+
A write runs under whatever credential the environment gives the command, and the store's IAM
|
|
232
|
+
decides whether it lands. On Google Cloud that is `CLOUDSDK_AUTH_ACCESS_TOKEN` when it is set, else
|
|
233
|
+
the Application Default Credentials, else the gcloud login; on AWS, `--profile`, else `AWS_PROFILE`.
|
|
230
234
|
`agent-secrets secret set NAME` replaces the value of a secret that exists. A new one is
|
|
231
|
-
`agent-secrets secret create NAME --owner me|shared --tier agent|human`.
|
|
235
|
+
`agent-secrets secret create NAME --owner me|shared|<email> --tier agent|human`. `--owner me` is
|
|
236
|
+
the email of the person the credential names, and is refused where it names none, as a token
|
|
237
|
+
minted for `cloud-platform` alone does: give `--owner <email>` there. Both read the value from
|
|
232
238
|
standard input or from a prompt with echo off, never from an argument. Type it at the prompt, so it
|
|
233
239
|
reaches no shell history.
|
|
234
240
|
|