Fix Fly.io deploy token quoting #121

Merged
eblume merged 1 commit from fix/fly-deploy-token into main 2026-02-08 02:43:46 -08:00
Owner

Summary

  • Strip literal quotes from Fly.io deploy token when syncing to Forgejo Actions secrets
  • The op CLI wraps values containing spaces in quotes; the Fly.io token format is FlyV1 <key> (contains a space)
  • This caused the CI deploy workflow to fail with a 401 auth error

Test plan

  • mise run provision-indri -- --tags forgejo_actions_secrets succeeds
  • Re-trigger deploy-fly workflow after merge — should authenticate successfully

🤖 Generated with Claude Code

## Summary - Strip literal quotes from Fly.io deploy token when syncing to Forgejo Actions secrets - The `op` CLI wraps values containing spaces in quotes; the Fly.io token format is `FlyV1 <key>` (contains a space) - This caused the CI deploy workflow to fail with a 401 auth error ## Test plan - [x] `mise run provision-indri -- --tags forgejo_actions_secrets` succeeds - [ ] Re-trigger deploy-fly workflow after merge — should authenticate successfully 🤖 Generated with [Claude Code](https://claude.com/claude-code)
The op CLI wraps values containing spaces in quotes. The Fly.io deploy
token (FlyV1 <key>) contains a space, causing the stored secret to
include literal quote characters and fail authentication.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit 6b1167a345 into main 2026-02-08 02:43:46 -08:00
eblume referenced this pull request from a commit 2026-02-08 02:43:48 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!121
No description provided.