@meffecta/agent 1.0.14 → 1.0.15
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/deployment.env.example +1 -1
- package/engine.json +2 -2
- package/lib/commands.js +1 -1
- package/lib/doctor.js +23 -1
- package/package.json +1 -1
- package/scripts/create-project.sh +2 -1
- package/scripts/deploy.sh +3 -3
- package/scripts/link-billing.sh +1 -1
- package/scripts/setup-infrastructure.sh +3 -2
- package/scripts/update-tooling.sh +1 -1
- package/scripts/verify-credentials.mjs +19 -5
package/deployment.env.example
CHANGED
|
@@ -52,5 +52,5 @@ REGION=europe-west1
|
|
|
52
52
|
# SCALING=scale-to-zero
|
|
53
53
|
# CPU=2
|
|
54
54
|
# MEMORY=4Gi
|
|
55
|
-
# MAX_INSTANCES=1 #
|
|
55
|
+
# MAX_INSTANCES=1 # the run pool is per process — >1 breaks it, so raise only with reason
|
|
56
56
|
# REQUEST_TIMEOUT=3600 # seconds one held request may last; the ceiling on a single run
|
package/engine.json
CHANGED
package/lib/commands.js
CHANGED
|
@@ -730,7 +730,7 @@ export const GROUPS = [
|
|
|
730
730
|
"Provision GCP: registry, buckets, service account, run queue, service shell",
|
|
731
731
|
script("setup-infrastructure.sh"),
|
|
732
732
|
],
|
|
733
|
-
["set-secret", "AGENT_API_SECRET --random,
|
|
733
|
+
["set-secret", "AGENT_API_SECRET --random, ANTHROPIC_API_KEY, GITHUB_TOKEN", script("set-secret.sh")],
|
|
734
734
|
["set-env", "GIT_REPO_URL — the one setting the service will not boot without", script("set-env.sh")],
|
|
735
735
|
["deploy", "Roll out an engine image and assert the runtime shape", script("deploy.sh")],
|
|
736
736
|
[
|
package/lib/doctor.js
CHANGED
|
@@ -216,7 +216,29 @@ export async function doctor() {
|
|
|
216
216
|
"meffecta-agent set-secret AGENT_API_SECRET (paste the same value, deploy, then delete the old one)",
|
|
217
217
|
);
|
|
218
218
|
}
|
|
219
|
-
|
|
219
|
+
// Either variable pays for runs, and the API key wins when both are set. Naming the one
|
|
220
|
+
// in effect matters more than naming a missing variable: a deployment that switched to a
|
|
221
|
+
// Console key and left the old token behind is still billing the key, not the subscription.
|
|
222
|
+
const claudeAuth = env.ANTHROPIC_API_KEY ? "ANTHROPIC_API_KEY" : "CLAUDE_CODE_OAUTH_TOKEN";
|
|
223
|
+
if (!env.ANTHROPIC_API_KEY && !env.CLAUDE_CODE_OAUTH_TOKEN) {
|
|
224
|
+
r.fail(
|
|
225
|
+
"No way to pay for runs",
|
|
226
|
+
"The engine needs ANTHROPIC_API_KEY (a Claude Console key — what a product or service should use) or CLAUDE_CODE_OAUTH_TOKEN (billed to a personal subscription).",
|
|
227
|
+
"meffecta-agent set-secret ANTHROPIC_API_KEY",
|
|
228
|
+
);
|
|
229
|
+
} else {
|
|
230
|
+
r.ok("Claude credential", `runs bill to ${claudeAuth}`);
|
|
231
|
+
if (env.ANTHROPIC_API_KEY && env.CLAUDE_CODE_OAUTH_TOKEN) {
|
|
232
|
+
r.warn(
|
|
233
|
+
"Both Claude credentials are set",
|
|
234
|
+
"ANTHROPIC_API_KEY outranks CLAUDE_CODE_OAUTH_TOKEN, so the subscription token is unused.",
|
|
235
|
+
// Both are secret-backed, so --remove-env-vars (what `set-env --unset` does) will not
|
|
236
|
+
// touch them. Removing one is --remove-secrets, which the CLI has no command for.
|
|
237
|
+
`Drop whichever you did not mean to bill: gcloud run services update ${d.SERVICE} --region=${d.REGION} --remove-secrets CLAUDE_CODE_OAUTH_TOKEN`,
|
|
238
|
+
);
|
|
239
|
+
}
|
|
240
|
+
}
|
|
241
|
+
for (const name of [apiSecretName, claudeAuth, "GITHUB_TOKEN"]) {
|
|
220
242
|
const ref = env[name]?.valueFrom?.secretKeyRef?.name;
|
|
221
243
|
if (!env[name]) {
|
|
222
244
|
r.fail(`${name} not set`, "Required by the engine.", `meffecta-agent set-secret ${name}`);
|
package/package.json
CHANGED
|
@@ -1,7 +1,8 @@
|
|
|
1
1
|
#!/usr/bin/env bash
|
|
2
2
|
set -euo pipefail
|
|
3
3
|
|
|
4
|
-
# Step 1 of
|
|
4
|
+
# Step 1 of the set-up (https://agent.meffecta.com/install): create the GCP project this
|
|
5
|
+
# deployment will live in.
|
|
5
6
|
#
|
|
6
7
|
# Give the agent a project of its own, separate from any product project it will read:
|
|
7
8
|
# its service account gets project-wide secret access, and the mail tokens stored here
|
package/scripts/deploy.sh
CHANGED
|
@@ -32,9 +32,9 @@ set -euo pipefail
|
|
|
32
32
|
# and is left alone.
|
|
33
33
|
#
|
|
34
34
|
# Usage:
|
|
35
|
-
# scripts/deploy.sh # the newest
|
|
36
|
-
# scripts/deploy.sh --tag
|
|
37
|
-
# scripts/deploy.sh --image europe-west1-docker.pkg.dev/PROJECT/REPO/agent:
|
|
35
|
+
# scripts/deploy.sh # the newest release (--tag latest)
|
|
36
|
+
# scripts/deploy.sh --tag 1.0.13 # a specific version, e.g. to roll back
|
|
37
|
+
# scripts/deploy.sh --image europe-west1-docker.pkg.dev/PROJECT/REPO/agent:1.0.13
|
|
38
38
|
# scripts/deploy.sh --dry-run # print the target, image and shape; change nothing
|
|
39
39
|
# scripts/deploy.sh --no-scheduler # roll out without re-syncing the triggers
|
|
40
40
|
#
|
package/scripts/link-billing.sh
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
#!/usr/bin/env bash
|
|
2
2
|
set -euo pipefail
|
|
3
3
|
|
|
4
|
-
# Step 2 of
|
|
4
|
+
# Step 2 of the set-up (https://agent.meffecta.com/install): link a billing account.
|
|
5
5
|
#
|
|
6
6
|
# Nothing else works without this — provisioning starts by enabling APIs, which fails on
|
|
7
7
|
# an unbilled project, and the failure does not mention billing.
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
set -euo pipefail
|
|
3
3
|
|
|
4
4
|
# One-time GCP provisioning for a deployment of the agent. Idempotent — safe to re-run.
|
|
5
|
-
# See
|
|
5
|
+
# See https://agent.meffecta.com/install for the whole set-up, of which this is step 5.
|
|
6
6
|
#
|
|
7
7
|
# Give the agent a GCP project of its OWN, separate from any product project it reads:
|
|
8
8
|
# this project's service account holds project-wide secret access, and the mail refresh
|
|
@@ -325,7 +325,8 @@ echo " Next, from this directory:"
|
|
|
325
325
|
echo ""
|
|
326
326
|
echo " $(cmd set-env) GIT_REPO_URL=https://github.com/<owner>/<content-repo>.git"
|
|
327
327
|
echo " $(cmd set-secret) AGENT_API_SECRET --random"
|
|
328
|
-
echo " $(cmd set-secret)
|
|
328
|
+
echo " $(cmd set-secret) ANTHROPIC_API_KEY # a Claude Console key — for a service"
|
|
329
|
+
echo " ...or CLAUDE_CODE_OAUTH_TOKEN # from: claude setup-token — individual use"
|
|
329
330
|
echo " $(cmd set-secret) GITHUB_TOKEN # must be able to clone the repo above"
|
|
330
331
|
echo " $(cmd deploy) # rolls out the engine, then creates its triggers"
|
|
331
332
|
if has_cli; then
|
|
@@ -23,7 +23,7 @@ set -euo pipefail
|
|
|
23
23
|
# That is this script's job, done by hand once. Afterwards:
|
|
24
24
|
#
|
|
25
25
|
# scripts/update-tooling.sh # match the newest published engine
|
|
26
|
-
# scripts/update-tooling.sh --tag
|
|
26
|
+
# scripts/update-tooling.sh --tag 1.0.13 # match a specific one, e.g. what you run
|
|
27
27
|
# scripts/update-tooling.sh --dry-run # show what would change, touch nothing
|
|
28
28
|
#
|
|
29
29
|
# Needs docker, and is the only thing here that does: the files are lifted out of the
|
|
@@ -619,7 +619,13 @@ async function checkDeploymentsContext() {
|
|
|
619
619
|
* These are also the ones a shipped script CAN test properly, because they are the
|
|
620
620
|
* engine's own and mean the same thing in every deployment.
|
|
621
621
|
*/
|
|
622
|
-
const ESSENTIAL = new Set([
|
|
622
|
+
const ESSENTIAL = new Set([
|
|
623
|
+
"AGENT_API_SECRET",
|
|
624
|
+
"ANTHROPIC_API_KEY",
|
|
625
|
+
"CLAUDE_CODE_OAUTH_TOKEN",
|
|
626
|
+
"GITHUB_TOKEN",
|
|
627
|
+
"GIT_REPO_URL",
|
|
628
|
+
]);
|
|
623
629
|
|
|
624
630
|
/**
|
|
625
631
|
* Inside a run, three of the four are proven by the fact that this output exists at all —
|
|
@@ -645,12 +651,20 @@ function checkPresence() {
|
|
|
645
651
|
// started it, which is exactly right, and means "unset" here would be a lie: the run
|
|
646
652
|
// doing the reporting is itself the proof it is set. AGENT_SPAWN_TOKEN is how we know we
|
|
647
653
|
// are inside a run; the engine sets that one, so `claude` has no reason to strip it.
|
|
648
|
-
|
|
649
|
-
|
|
654
|
+
//
|
|
655
|
+
// Either variable pays for runs, and the API key wins when both are set — so report which
|
|
656
|
+
// one is actually in play rather than just that something is.
|
|
657
|
+
if (env.ANTHROPIC_API_KEY) {
|
|
658
|
+
ok("ANTHROPIC_API_KEY", "present — runs bill to this Console key (not remotely testable)");
|
|
659
|
+
if (env.CLAUDE_CODE_OAUTH_TOKEN) {
|
|
660
|
+
ok("CLAUDE_CODE_OAUTH_TOKEN", "present but unused — the API key outranks it");
|
|
661
|
+
}
|
|
662
|
+
} else if (env.CLAUDE_CODE_OAUTH_TOKEN) {
|
|
663
|
+
ok("CLAUDE_CODE_OAUTH_TOKEN", "present — runs bill to this subscription (not remotely testable)");
|
|
650
664
|
} else if (env.AGENT_SPAWN_TOKEN) {
|
|
651
|
-
ok("
|
|
665
|
+
ok("Claude credential", "in use by this very run — a run cannot read it, by design");
|
|
652
666
|
} else {
|
|
653
|
-
skip("
|
|
667
|
+
skip("Claude credential", "neither ANTHROPIC_API_KEY nor CLAUDE_CODE_OAUTH_TOKEN is set");
|
|
654
668
|
}
|
|
655
669
|
// Either name satisfies the engine; say which one is actually in play.
|
|
656
670
|
if (env.AGENT_API_SECRET) {
|