QOL: Extending zarf connect usability
#575
Closed
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
YrrepNoj
force-pushed
the
qol/port-auto-choosing
branch
from
95e0008
to
b3e0478
Compare
|
We should probably look at these together 😆 b350f4e |
|
...or at least make sure that the change isn't already in #511 |
|
Closing as this was also implemented in #586 |
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.
Zarf Connect Default Stability
Add logic so default
zarf connectcommands will auto-detect when the standard ports are already being used and use a random open one instead of failing the command.Zarf Connect Usability Improvement
Add a utility function so users can figure out which
zarf connectcommands are available from packages that have already been installed. Super useful for people who are not familiar with the packages that has already been deployed to a cluster.