[
https://issues.apache.org/jira/browse/LIBCLOUD-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746547#comment-13746547
]
ASF subversion and git services commented on LIBCLOUD-375:
----------------------------------------------------------
Commit f6239257287cc1303dd3ee77f224f7d529d4066d in branch refs/heads/trunk from
[~kami]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=f623925 ]
Modify EC2 driver create_node method and make extension argument for assigning
a node to a security group consistent with the OpenStack implementation.
Previously the argument was called ex_securitygroup, now it's called
ex_security_groups.
Part of LIBCLOUD-375.
> Unify ex argument for security groups of create_node for AWS and OpenStack
> --------------------------------------------------------------------------
>
> Key: LIBCLOUD-375
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-375
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: Ivan
> Priority: Trivial
>
> When creating a new node, OpenStack and AWS use different names for ex
> argument for security groups although the underlying feature is the same.
> OpenStack uses 'ex_security_groups'
> AWS uses 'ex_securitygroup'
> Proposed solution: rename AWS argument to match OpenStack's. (as both support
> multiple groups)
> https://github.com/ikusalic/libcloud/compare/unify-ex-security-groups
> If this is problem because it is not backwards compatible, maybe adding alias
> 'ex_security_groups' to AWS makes sense.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
