ci: disable premature DFX server deploy workflows until migration#3815
Merged
Conversation
The dfx-api-dev/prd workflows SSH-deploy to dfxdev/dfxprd, but the migration is not live yet — the API still runs on Azure. Their push triggers made every develop/main merge fail at the SSH deploy step (server-side prerequisites not in place). Restrict both to workflow_dispatch until the cutover.
davidleomay
approved these changes
Jun 3, 2026
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
2 participants
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.
Summary
dfx-api-dev.yaml/dfx-api-prd.yaml(added in feat: Docker + SSH deploy for DFX server migration #3810) SSH-deploy the API container to the DFX servers. The migration is not live yet — the API still runs on Azure (api-dev.yaml/api-prd.yamlremain the active deploy path).pushtriggers (develop/main) made every merge fail at the SSHDeploystep, because the documented server-side prerequisites (deploy.shdfx-apicase,authorized_keys, compose) are not in place yet.workflow_dispatch(manual) so they no longer break branch CI. The build/push + deploy can still be run on demand to validate the migration setup.Why
Failing run example:
DFX API DEV CI/CDondevelop→Too many authentication failures/Permission deniedat the SSH deploy step. The live Azure pipeline was unaffected the whole time.Restoring auto-deploy
When the migration goes live, re-add the
pushtrigger to each workflow (the previous config is preserved in git history / inline comment).Test plan
API PR CI) is green (no TS/source changes; build/lint/test unaffected).DFX API DEV CI/CD.API DEV CI/CD(Azure) still runs and stays green.