[
https://issues.apache.org/jira/browse/JCLOUDS-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097207#comment-14097207
]
ASF subversion and git services commented on JCLOUDS-661:
---------------------------------------------------------
Commit 7070016cd98b604bedb25d757496546c122b6c92 in jclouds-labs-google's branch
refs/heads/master from [~hendrens]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs-google.git;h=7070016 ]
JCLOUDS-661: Supporting single port firewall rules in GCE
Corresponding test added in
https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=f3778b6
> Can not create a single port firewall rule using google SecurityGroupExtension
> ------------------------------------------------------------------------------
>
> Key: JCLOUDS-661
> URL: https://issues.apache.org/jira/browse/JCLOUDS-661
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-labs-google
> Affects Versions: 1.7.3, 1.8.0
> Reporter: Stuart Hendren
> Priority: Minor
> Labels: easyfix
> Attachments: JCLOUDS-661.patch
>
>
> When adding a new IpPermission for a SecurityGroup using the google
> implementation of the SecurityGroupExtension you cannot specify a single
> port.
> The IpPermission requires a to and from port, then the implementation
> (GoogleComputeEngineSecurityGroupExtension) fails if these two ports are the
> same. This works with the AWS implementation, so I guess is the correct way
> to specify a single port with this API.
> Should be fixable with a simple check and using addPort(Integer port) from
> the builder.
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
