-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cli/compose: implement the ports validation method #5524
Merged
thaJeztah
merged 1 commit into
docker:master
from
Stavrospanakakis:compose-ports-validation
Oct 10, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not for this PR, but we probably would be able to use the same utilities for this case as well, which could be either using
ParsePortSpec
and making sure the IP address is not set, or a combination ofParsePortRange
andSplitProtoPort
.I see the latter is the approach taken for the
--expose
flag, but .. I'm actually wondering if the first approach would be better, because it also validates the given protocli/cli/command/container/opts.go
Lines 443 to 466 in 305985c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, MAYBE validating the proto shouldn't belong on the client-side, as the list of supported protocols could depend on what the daemon supports.
But given that we already do it elsewhere, maybe that's not too problematic (and if we change, we should do so across the board).
We could possibly convert the code linked above to a utility if we don't want to duplicate the logic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In any case, none of the above is needed for the current PR; it's mostly outlining thoughts for a follow-up 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thaJeztah The
ParsePortSpec
method returnsPortMapping
while theexpose
propery is aPortBinding
, soParsePortSpec
might not be the best for this case.For this reason, I believe that the combination of
ParsePortRange
andSplitProtoPort
will work better .Regarding creating a utility, I am not sure that it will help to avoid duplicate code. For example:
Using a utility:
Not using a utility:
Both cases with or without a utility contain duplicate code.
What do you think?
I will be happy to open a new pull request for this.