[
https://issues.apache.org/jira/browse/JCLOUDS-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera updated JCLOUDS-1290:
------------------------------------
Component/s: jclouds-compute
> Inconsistency in IpPermission.groupId()
> ---------------------------------------
>
> Key: JCLOUDS-1290
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1290
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 2.0.1
> Reporter: Svetoslav Neykov
> Labels: aws-ec2
>
> When trying to add {{IpPermission}} allowing access from an existing
> {{SecurityGroup}} how should we initialise the {{IpPermission.groupId}} field
> from the {{SecurityGroup}} fields so it works across clouds?
> Using {{IpPermission.groupId == SecurityGroup.id()}} works for:
> * OpenStack (Bluebox)
> * Azure ARM
> Doesn't work for:
> * Amazon (Invalid id: "eu-west-1/sg-eb0a4292" (expecting "sg-..."))
> Using {{IpPermission.groupId == SecurityGroup.providerId()}} works for:
> * Amazon
> * Azure ARM
> Doesn't work for:
> * OpenStack (Bluebox) (id must be in format regionId/id)
> My understanding is that it should always work with {{SecurityGroup.id()}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
