Repository navigation
feat(cli): support multiple local deployments and configurable host ports - #28
Merged
Merged
Conversation
Allow remapping or disabling Runtime debug and adapter host ports. Use selected ports and project for preflight, persist settings, and preserve them during upgrades while supporting legacy records. Fixes #26
…-discovery # Conflicts: # README.md # README_CN.md # README_ES.md # README_FR.md # README_JP.md # README_KO.md # README_RU.md # README_TW.md # README_VI.md
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.
Multiple local deployments shared a single discovery record and fixed host ports, so installing another instance could conflict with an existing one. This change discovers and selects deployments through contexts and makes each installation's Compose project and published host ports configurable.
context list --discover, and select local lifecycle targets through the existing context/endpoint flow, rejecting ambiguous matches.install --project,--plugin-debug-port(0disables publishing), and--adapter-ports(nonedisables publishing). Use the same settings for preflight and Compose generation, persist them for upgrades, and preserve legacy deployments and container-side ports.Validation:
go test ./...,go vet ./..., build/help/schema checks, and Docker Compose parsing for default, custom, and disabled port publishing passed locally. Regression tests cover occupied ports, multiple projects, persisted settings, legacy records, upgrades, and context selection. No live container startup was performed because the local Docker daemon is unavailable; cross-platform race checks run in CI.Fixes #26