[
https://issues.apache.org/jira/browse/LIBCLOUD-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044757#comment-14044757
]
ASF GitHub Bot commented on LIBCLOUD-586:
-----------------------------------------
GitHub user zerthimon opened a pull request:
https://github.com/apache/libcloud/pull/326
[LIBCLOUD-586] allow EC2SecurityGroup objects be specified when creating...
... nodes, also use different parameters when launching node into a subnet
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zerthimon/libcloud
LIBCLOUD-586_security_group_ids_4_create_node
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/326.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #326
----
commit 12c13cf7afcba6c4eebb09f673128af20a9f30f5
Author: Lior Goikhburg <goikhb...@gmail.com>
Date: 2014-06-26T15:24:23Z
[LIBCLOUD-586] allow EC2SecurityGroup objects be specified when creating
nodes, also use different parameters when launching node into a subnet
----
> Allow security group IDs be specified when launching a node into a subnet
> -------------------------------------------------------------------------
>
> Key: LIBCLOUD-586
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-586
> Project: Libcloud
> Issue Type: Improvement
> Reporter: Lior Goikhburg
> Priority: Minor
>
> This requires using SecurityGroupId.n parameters instead of SecurityGroup.n
--
This message was sent by Atlassian JIRA
(v6.2#6252)
