NOJIRA-Bm-ssh-deploy-rollout-all-services - #1186
Merged
Merged
Conversation
- monorepo: roll out the bm-nyc-01 direct-SSH deploy pattern (piloted for bin-call-manager) to 31 more bin-*-manager services, replacing each service's GKE -release job with a -deploy job that runs .circleci/scripts/ssh-deploy.sh: bin-agent-manager, bin-api-manager, bin-billing-manager, bin-campaign-manager, bin-ai-manager, bin-contact-manager, bin-conference-manager, bin-conversation-manager, bin-customer-manager, bin-direct-manager, bin-email-manager, bin-flow-manager, bin-hook-manager, bin-message-manager, bin-number-manager, bin-outdial-manager, bin-pipecat-manager, bin-queue-manager, bin-rag-manager, bin-registrar-manager, bin-route-manager, bin-schedule-manager, bin-storage-manager, bin-tag-manager, bin-talk-manager, bin-timeline-manager, bin-transcribe-manager, bin-transfer-manager, bin-tts-manager, bin-webchat-manager, bin-webhook-manager - monorepo: bin-sentinel-manager deliberately excluded from the rollout and left on its original GKE -release job - it requires the Kubernetes API (rest.InClusterConfig) and has no bm-nyc-01 compose-service equivalent (voipbin/voipbin's install/docker-compose.yml.dist and sync-compose-images.sh's LOCK_ONLY_IMAGES both document this exclusion) - monorepo: simplify the approval flow for all bm-nyc-01-deploying services (including bin-call-manager, retroactively) to a single build-approval gate covering test/build/deploy - matches the old GKE release job's convenience, since bm-nyc-01 doubles as our only environment and a second deploy-specific approval added friction without a distinct safety benefit - monorepo: remove the now-fully-unreferenced docker-release shared command and gcloud_image anchor for the 31 migrated services, while restoring/keeping both for bin-sentinel-manager, the one remaining GKE deploy
- monorepo: document the new bm-nyc-01 SSH deploy path in README.md for all 31 rolled-out services (agent, api, billing, campaign, ai, contact, conference, conversation, customer, direct, email, flow, hook, message, number, outdial, pipecat, queue, rag, registrar, route, schedule, storage, tag, talk, timeline, transcribe, transfer, tts, webchat, webhook-manager); bin-webchat-manager had no README, so a minimal one was created - monorepo: document bin-sentinel-manager's exclusion from the rollout (stays on GKE) in its README
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rolls out the bm-nyc-01 direct-SSH deploy pattern, already piloted and production-verified for bin-call-manager, to 31 more bin-*-manager services. Each service's GKE -release job is replaced with a -deploy job that runs .circleci/scripts/ssh-deploy.sh, bumping that service's pin on bm-nyc-01's live versions.lock/docker-compose.yml and recreating the container. Also documents the new deploy path in each affected service's README.md.