mirror of https://github.com/apache/jclouds.git
474aa52da9
When the security group is not generated by jclouds (e.g. when using a custom group, or when in a VPC which generally requires its own security groups), the group name to launch nodes into is lost, since it is parsed from the generated security group ID. This patch introduces a very local workaround: try to parse the name from the key name, which if generated by jclouds has a format that is very similar to the generated security group ID. While probably not the ideal solution for persisting the group name either (using user metadata might be), this fixes a blocking issue for scenarios where you can't use a generated security group ID (using a VPC in our case), but you can use a generated key pair name. Also it shouldn't interfere with existing usage: if a name can be parsed from the security group, that is used, and if the key name is not generated, the behaviour remains as it currently is (group name is null if it can't be parsed from the security group). |
||
|---|---|---|
| .. | ||
| src | ||
| README.txt | ||
| pom.xml | ||
README.txt
====
Licensed to jclouds, Inc. (jclouds) under one or more
contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. jclouds 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.
====
#
# The jclouds API for Amazon's EC2 service (http://aws.amazon.com/ec2/).
#
# TODO: Implementation status.
# TODO: Supported features.
# TODO: Usage example.