Skip to content

fix(paw): authenticate publish_app/update_app to Genesis with genesis_token - #402

Open
rita-aga wants to merge 1 commit into
mainfrom
claude/agent-publish-app-tool
Open

fix(paw): authenticate publish_app/update_app to Genesis with genesis_token#402
rita-aga wants to merge 1 commit into
mainfrom
claude/agent-publish-app-tool

Conversation

@rita-aga

Copy link
Copy Markdown
Collaborator

The agent tools temper.publish_app()/update_app() already pushed bundles to Genesis + registered versions, but attached no credential — only X-Tenant-Id. So the git push failed with could not read Username (the exact error agents hit) and OData calls were unauthenticated.

This attaches the genesis_token GitToken as Authorization: Bearer on both the git push (a second http.<url>.extraHeader) and the registry OData calls, and returns a clear error if the secret is unset instead of the cryptic git failure. Pure helper genesis_bearer() is unit-tested; wasm builds clean.

Companion to #400 (which seeds genesis_token into the vault). With both deployed, agents can publish to Genesis via temper.publish_app end-to-end.

…_token

temper.publish_app()/update_app() pushed app bundles to the Genesis
registry and called its OData actions with only an X-Tenant-Id header and
no credential, so the git push failed with "could not read Username" (no
tty to prompt) and registry calls were unauthenticated.

Attach the genesis_token GitToken as Authorization: Bearer on both the git
push (a second http.<url>.extraHeader) and the registry OData calls, and
fail with a clear message if the secret is unset instead of the cryptic
git error. genesis_bearer() is unit-tested.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant