feat(framework): --deploy actually ships via real deploy targets#170
Merged
Conversation
Wire ai-autopilot's cloudflareTarget/dokployTarget into the framework CLI so
--deploy cloudflare / --deploy dokploy execute the deploy, not just narrate a
plan-only decision.
- hostExecutor: a DeployExecutor that runs commands (wrangler) in the agent's
host workspace (LocalRunner can't - it mkdtemps a fresh dir and deletes it)
- deployWith step: run a real DeployTarget against the decided plan
- runFramework: optional deployTarget executes the plan; else plan-only narrate
- CLI: --cf-project / --dokploy-url / --dokploy-app; dokploy config validated
- --fake stays plan-only and deterministic
Targets never throw on missing creds (report { deployed: false }). 34 tests;
--help + fake e2e + dokploy-misconfig verified.
suleimansh
added
enhancement
7 tasks
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.
Follow-up to #166.
framework --deploy <target>now ships the app instead of narrating a plan-only decision, by wiring the deploy targets that already exist in@gemstack/ai-autopilot.--deploy cloudflareruns install/build/wranglerin the agent's workspace (SSR to Workers, SSG/SPA to Pages). It needs a host executor bound to that cwd becauseLocalRunnercan't be reused here (it mkdtemps a fresh dir and deletes it on dispose) - so this addshostExecutor.--deploy dokployis a fetch to a self-hosted instance (--dokploy-url+--dokploy-apprequired).--deploy <name>just narrates the decision, as before.Creds come from the env (
CLOUDFLARE_API_TOKEN/DOKPLOY_AUTH_TOKEN); the targets never throw on missing config, they report{ deployed: false }.--fakestays plan-only and deterministic.New pieces:
hostExecutor, thedeployWithstep,runFramework({ deployTarget }), and the CLI flags. 34 tests, full-repo typecheck + build green; verified--help, the fake e2e, and the dokploy-misconfig error path. Live cloudflare/dokploy shipping is infra-gated (needs a token). Changeset included.