[Feat] Show target instance before deploy, stop, destroy and compact - #64
Merged
Merged
Conversation
bean1352
marked this pull request as draft
September 2, 2026 12:19
bean1352
marked this pull request as ready for review
September 2, 2026 12:38
LucDeCaf
previously approved these changes
Sep 2, 2026
LucDeCaf
left a comment
Contributor
There was a problem hiding this comment.
I like this idea, looks good 👍
bean1352
marked this pull request as draft
September 3, 2026 08:41
This was referenced Sep 3, 2026
Closed
bean1352
marked this pull request as ready for review
September 3, 2026 10:26
LucDeCaf
previously approved these changes
Sep 3, 2026
LucDeCaf
left a comment
Contributor
There was a problem hiding this comment.
Tested this on my side, looks good
bean1352
force-pushed
the
feat/show-target-instance
branch
from
September 16, 2026 10:26
e54b0cd to
771ec23
Compare
LucDeCaf
approved these changes
Sep 17, 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
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.
What
Prints the resolved instance name and IDs before
deploy,deploy sync-config,deploy service-config,stop,destroyandcompactdo anything, so you can see which instance is about to change.statusprints the target first as well, with the API URL for self-hosted instances. JSON and YAML output are unchanged.deployanddeploy service-configalso warn whenservice.yamlhas a differentnamethan the instance, because deploying renames it.Dry run
All deploy commands accept
--dry-run. It prints the target instance, runs the validations, and stops before deploying or provisioning. It also shows what would change:When the instance is deprovisioned, a real deploy provisions it first. The dry run says so and skips the sync config validation that needs a running instance.
stopanddestroyalready require--confirm=yes, so they are unchanged.Notes
diff(jsdiff) as a direct dependency of the CLI. It was already in the lockfile as a transitive dependency.secret: !env ...always showreplicationas changed, because the value is sent again. This is documented in the usage docs.AI disclosure
I used Claude to research the codebase and implement the change. I reviewed and tested it myself.