This repository has been archived by the owner on Jul 14, 2023. It is now read-only.
auto-connect as subcommand #882
Open
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why?
If we specify
--auto-connectflag fromdraft up, we will be able to connect, but we will not reuse environment flag from command-line. More than that, if we specifydraft connectflags (dry-run, override-port, container, etc) indraft up --auto-connect, the command line will no be able to detect those flag.> draft up --auto-connect --dry-run Error: unknown flag: --dry-runSee issue #879.
How?
Use
auto-connectas the subcommand ofdraft up.Usage:
> draft up [up flags] auto-connect [auto-connect flags]