feat(deploy): add config deploy and agent installers#17
Open
nonozone wants to merge 1 commit into
Open
Conversation
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
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
Adds a CLI-only deployment workflow for moving a working Clipal setup to another machine and quickly preparing AI agent CLIs there. This lets users export/import Clipal config without opening the Web UI, then install and optionally apply existing Clipal takeover for selected agents.
Changes
clipal exportandclipal import <file>.clipal deploy [package] [agent...]for importing config, installing missing agent CLIs, and applying Clipal takeover.clipal install [agent...]for install-only flows without takeover.The existing Clipal provider config schema, routing behavior, Web UI, and takeover implementation are left intact; this PR adds CLI entry points around them.
Verification
go test -count=1 ./...