Token: proxy-1 reuses VPS-1's existing vault_netbird_proxy_token — a shared token + same NB_PROXY_DOMAIN is a valid NetBird HA cluster, so the separate vault_netbird_proxy1_token (and its generate-on-mgmt step) is gone. No new vault secret needed.
Pipeline:deploy-netbird-proxy now only runs on master + manual, so it stops auto-failing on feature-branch pushes.
🤖 Generated with Claude Code
Follow-up to #47.
- **Token:** proxy-1 reuses VPS-1's existing `vault_netbird_proxy_token` — a shared token + same `NB_PROXY_DOMAIN` is a valid NetBird HA cluster, so the separate `vault_netbird_proxy1_token` (and its generate-on-mgmt step) is gone. No new vault secret needed.
- **Pipeline:** `deploy-netbird-proxy` now only runs on master + manual, so it stops auto-failing on feature-branch pushes.
🤖 Generated with Claude Code
- Drop the invented per-instance token: a shared NB_PROXY_TOKEN with the
same NB_PROXY_DOMAIN is a valid HA cluster, so proxy-1 just reuses the
existing vault_netbird_proxy_token. No token to generate, no new vault
secret — removes that deploy gate entirely.
- Scope the deploy-netbird-proxy pipeline to master + manual so it stops
auto-running (and failing) on feature-branch pushes.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #47.
vault_netbird_proxy_token— a shared token + sameNB_PROXY_DOMAINis a valid NetBird HA cluster, so the separatevault_netbird_proxy1_token(and its generate-on-mgmt step) is gone. No new vault secret needed.deploy-netbird-proxynow only runs on master + manual, so it stops auto-failing on feature-branch pushes.🤖 Generated with Claude Code
claude-bot referenced this pull request2026-09-25 07:29:40 +00:00