ci: use Docs Agent API key so per-agent secrets are available#210
ci: use Docs Agent API key so per-agent secrets are available#210dannyneira wants to merge 0 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR updates the release docs update workflow to authenticate warpdotdev/oz-agent-action with the Docs Agent-scoped API key so that the agent's per-agent secrets are available during the cloud run, and removes the now-unneeded profile input.
Concerns
- No blocking correctness or security concerns found in the annotated diff.
- No approved or repository spec context was provided, so implementation-vs-spec drift was not applicable.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
dannyneira
force-pushed
the
danny/docs-agent-api-key
branch
from
27482cb to
b46a355
Compare
1 participant
Summary
Replaces
WARP_API_KEYwithDOCS_AGENT_WARP_API_KEYin the release docs update workflow. Running under the Docs Agent's own API key makes its per-agent secrets (includingDOCS_AGENT_GRAFANA_TOKEN) available in the cloud run environment — without needing to add the Grafana token to the shared Oz team secrets.Setup required
Generate an API key for the Docs Agent on prod Oz:
oz.warp.dev/agents/019eb332-2ee0-7417-8ecc-89260cf5b850 → Settings → API Keys → Create
Add it as a GitHub Actions secret in
warpdotdev/docs:Settings → Secrets and variables → Actions → New repository secret →
DOCS_AGENT_WARP_API_KEYWhy this works
The
oz-agent-actionprofileinput only selects a behavioral profile (model, instructions) — it does not inject per-agent secrets. The API key determines which agent identity runs and therefore which per-agent secrets are available. Using the Docs Agent's own key scopes the entire run to that agent.Related
Co-Authored-By: Oz oz-agent@warp.dev