Repository navigation
VPC ACL: keep the ports and ICMP type of rules given by protocol number or as upper-case ICMP #14357
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
Open
bhouse-nexthop
wants to merge
4
commits into
apache:4.22
Choose a base branch
from
bhouse-nexthop:fix-acl-protocol-number-ports
base: 4.22
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+249
−20
Open
VPC ACL: keep the ports and ICMP type of rules given by protocol number or as upper-case ICMP #14357
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
3495705
Keep the ports and ICMP type of ACL rules given by protocol number
bhouse-nexthop a54b84a
Keep protocol 6 and 17 without ports as the whole protocol
bhouse-nexthop e32fbb8
Describe why protocol 6 and 17 without ports stay numbers without rel…
bhouse-nexthop 252038f
Move the protocol number helpers to NetUtils
bhouse-nexthop 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 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
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
44 changes: 44 additions & 0 deletions
44
...test/java/org/apache/cloudstack/api/command/user/network/UpdateNetworkACLItemCmdTest.java
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| // Licensed to the Apache Software Foundation (ASF) under one | ||
| // or more contributor license agreements. See the NOTICE file | ||
| // distributed with this work for additional information | ||
| // regarding copyright ownership. The ASF licenses this file | ||
| // to you under the Apache License, Version 2.0 (the | ||
| // "License"); you may not use this file except in compliance | ||
| // with the License. You may obtain a copy of the License at | ||
| // | ||
| // http://www.apache.org/licenses/LICENSE-2.0 | ||
| // | ||
| // Unless required by applicable law or agreed to in writing, | ||
| // software distributed under the License is distributed on an | ||
| // "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY | ||
| // KIND, either express or implied. See the License for the | ||
| // specific language governing permissions and limitations | ||
| // under the License. | ||
| package org.apache.cloudstack.api.command.user.network; | ||
|
|
||
| import org.junit.Assert; | ||
| import org.junit.Test; | ||
| import org.springframework.test.util.ReflectionTestUtils; | ||
|
|
||
| public class UpdateNetworkACLItemCmdTest { | ||
|
|
||
| private String protocolOf(String protocol) { | ||
| UpdateNetworkACLItemCmd cmd = new UpdateNetworkACLItemCmd(); | ||
| ReflectionTestUtils.setField(cmd, "protocol", protocol); | ||
| return cmd.getProtocol(); | ||
| } | ||
|
|
||
| @Test | ||
| public void getProtocolTreatsProtocolNumberOneAsIcmp() { | ||
| // as createNetworkACL does, so that the rule keeps its icmp type and code | ||
| Assert.assertEquals("icmp", protocolOf("1")); | ||
| Assert.assertEquals("icmp", protocolOf(" 1 ")); | ||
| } | ||
|
|
||
| @Test | ||
| public void getProtocolLeavesOtherProtocolsAlone() { | ||
| Assert.assertEquals("tcp", protocolOf(" tcp ")); | ||
| Assert.assertEquals("47", protocolOf("47")); | ||
| Assert.assertNull(protocolOf(null)); | ||
| } | ||
| } |
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
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
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
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
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
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
Oops, something went wrong.
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.
@bhouse-nexthop thanks for the update.
should we consider
updateNetworkACLItemCmd.getSourcePortStart(), and thennetworkACLItemVo.getSourcePortStart()?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.
@weizhouapache good question. It already works that way when the protocol is given. This check runs after
transferDataToNetworkAclRulePojo(), so on a partial updatenetworkACLItemVo.getSourcePortStart()already holds the command's port if one was passed, and the stored port if not. That is "the command's value, then the rule's value".When the protocol is not given, I check only the ports in the command on purpose. Using the rule's stored ports there would re-check ports the caller didn't touch. A rule stored before this change with ports on, for example, protocol
47would then be rejected for any edit at all, even changing onlyreasonornumber, until someone removes the ports. So in that case only ports passed in this call are checked against the stored protocol. A protocol change is always checked against the ports the rule ends up with (validatePortsAreUsableWithProtocolOnUpdateTestStoredPortsKeptWhenProtocolNotGiven/...TestProtocolChangedOntoStoredPortscover both).If you would rather we reject any edit of such a rule until its ports are fixed, I can switch it to always use the rule's values. It's a one-line change.