This plugin was deprecated and replaced with a new plugin, named EC-AWS-EC2. The new plugin has a similar set of capabilities, like working with environment templates, provisioning instances etc. It is using an updated version of Amazon SDK. Please consider using the new plugin.
To compile this plugin, run ./gradlew.
Plugin configurations are sets of parameters that apply across some or all of the plugin procedures. They reduce repetition of common values, create predefined sets of parameters for end users, and store credentials securely. Each configuration has a unique name that is automatically entered in designated parameters in the procedures.
Go to Administration > Plugins to open the Plugin Manager.
Find the EC-EC2 row.
Click Configure to open the EC2 Configurations page.
Click Create Configuration.
To create a EC2 configuration, enter the following information and click OK.
Remember that you may need to create additional configurations later.
| Parameter | Description |
|---|---|
Configuration Name |
Provide a unique name for the connection, keeping in mind that you may need to create additional connections over time. (Required) |
Description |
A description for this configuration. The default is EC2 integration. |
Service URL |
The service URL for the EC2 service. For the Amazon public EC2, this should be https://ec2.amazonaws.com. (Required) |
Resource Pool to use |
The name of the pool of resources on which the plugin procedure steps can run. The default is default (Required) |
Workspace |
The workspace to use for resources dynamically created by this configuration. The default is default. (Required) |
Access Key (Credential Parameters) |
The Access Key ID and Secret Access Key, that are required for communicating with EC2. The configuration stores these as a credential. (Required) |
Attempt Connection? |
If the check box is selected, the system tries a connection to check credentials. (Required) |
Debug Level |
The debug level for the output (Required):
The default is 1. |
HTTP Proxy |
A HTTP proxy that should be used for connections. |
Proxy Authorization |
Username and password used to connect to HTTP proxy. |
The EC2 Configurations page now shows the new configuration.
This procedure allocates a public IP address using the Amazon EC2 API. You run this procedure to get an Elastic IP address to use with your EC2 account.
-
Go to the API_AllocateIP procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Results Location |
Where to put the result. If you do not enter a location, the result is only printed. |
This procedure attaches a previously allocated IP address to an instance. This procedure associates an Elastic IP address with the instance. If the IP address is currently assigned to another instance, it is re-assigned to the instance.
-
Go to the API_AssociateIP procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Instance |
The instance to associate with the IP address. (Required) |
Elastic IP |
IP address to assign to the instance. (Required) |
This procedure attaches a list of volumes to a list of instances, using the order of both lists to match volumes to instances. It attaches each Amazon EBS volume to a running instance and exposes it as the specified device.
-
Go to the API_AttachVolumes procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Device |
How the device is exposed to the
instance. The default is |
List of Instances |
The instances to which the volumes are attached. (Required) |
List of Volumes |
The volumes that are attached to the instances. (Required) |
This procedure converts a running instance into a new image. It creates an Amazon EBS-backed AMI from an Amazon EBS-backed instance.
-
Go to the API_CreateImage procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Instance |
The name of the instance to convert. (Required) |
New Image Name |
The name of the new image. (Required) |
New Image Description |
The description for the new image. (Required) |
No Reboot |
By default, this parameter is set to False. Amazon EC2 tries to shut down the instance cleanly before the new image is created. Amazon EC2 then restarts the new instance with the new image. When the parameter is set to True, Amazon EC2 does not shut down the instance before creating the image, and the file system integrity on the new image cannot be guaranteed. (Required) |
Results Location |
Where to put the result. If you do not enter a location, the result is only printed. (Required) |
This procedure creates a new key pair with the specified name. If a key with the specified name already exists, Amazon EC2 returns an error. The public key is stored by Amazon EC2, and the private key file is saved in the job workspace with read permission for the user running the agent. The private key file name is the key pair name, with .pem as extension.
Important: You should retrieve the private key file from the job workspace and save it in a secure place. You will need the private key file in order to connect (using SSH or Windows Remote Desktop) to any EC2 instance that was launched using the key pair name.
-
Go to the API_CreateKey procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Key name |
A unique name for the key pair. The
default is |
Results Location |
Where to put the result. If the location is not specified, the result is only printed. |
This procedure allows you to create a new subnet within Amazon VPC by specifying its name, CIDR block, VPC ID and availability zone.
-
Go to the API_CreateSubnet procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Subnet Name |
Name to be given to subnet. |
CIDR Block |
The range of IP addresses to use in the subnet in CIDR format (for example, 10.0.0.0/24). The range of IP addresses in the subnet must be subset of IP address in the VPC. The size subnet can equal the size of the VPC. (Required) |
Availability Zone |
Availability zone where this subnet will reside. If no preferences are entered, Amazon will choose an availability zone for you. (Required) |
VPC ID |
VPC to use for this subnet. (Required) |
Results Location |
Where to put the result. If not specified, the result is only printed. |
This procedure adds or overwrites one or more tags for the specified Amazon EC2 resources.
-
Go to the API_CreateTags procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Resources |
A list of resource IDs, separated by spaces. (Required) |
Tags |
A list of key-value pairs, separated by commas, in this format: key1 ⇒ value1, key2 ⇒ value 2, … (Required) |
Amazon Virtual Private Cloud (Amazon VPC) lets you provision a logically isolated section of the Amazon Web Services (AWS) Cloud where you can launch AWS resources in a virtual network that you define. This procedure allows you to create a new Amazon VPC by specifying the VPC name and CIDR block.
-
Go to the API_CreateVPC procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
VPC Name |
Name to be given to VPC. |
CIDR Block |
The range of IP addresses to use for your VPC, in CIDR format, for example,10.0.0.0/24.Block size must be between a /16 netmask and /28 netmask. (Required) |
Results Location |
Where to put the result. If not specified, the result is only printed. |
This procedure deletes the specified key pair by removing the public key from Amazon EC2. You must own the key pair.
-
Go to the API_DeleteKey procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Key name |
The name of the key pair to delete. The
default is |
This procedure deletes an EBS volume. It is usually used to delete a volume created for a specific instance.
-
Go to the API_DeleteVolume procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Detach Only? |
If the check box is selected, the volume is not deleted after it is detached from the instance. (Required) |
Volume |
Name of volume to delete. |
This procedure allows you to delete the VPC and any subnets created within it by specifying the VPC ID.
-
Go to the API_DeleteVPC procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
VPC ID |
ID of VPC to delete. (Required) |
Results Location |
Where to put the result. If not specified, the result is only printed. |
This procedure adds descriptions to one or more instances.
-
Go to the API_DescribeInstances procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Instances |
One or more instances. You can specify one instance, a list of instances separated with semi-colons, or reservation. |
Results Location |
Where to put the result. If the location is not specified, the result is only printed. |
This procedure releases a public IP address allocated to your account.
-
Go to the API_ReleaseIP procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Elastic IP |
The IP address to be released. (Required) |
This procedure runs the specified API method (procedure). Individual API procedures collect parameter values and call this procedure. Credentials should be attached to this procedure.
-
Go to the API_Run procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Method |
The API method (procedure) to run. (Required) |
This procedure allows the user to start one or more instances from a machine image (AMI/EMI). The instances are part of one reservation and can be terminated later as a group or individually.
| Parameter | Description |
|---|---|
Configuration |
The name of the config which holds all the connection information. This must reference a valid existing configuration. (Required) |
Number of Instances |
The number of instances to
start(default is |
Security Group |
The security group to use (default is
|
Image |
The name of the EC2 image that you would like to deploy. (Required) |
Instance Type |
The instance type (default is
|
Key name |
The name of the key pair to use. (Required) |
Results Location |
Where to put the result. If not specified, the result is only printed. |
User Data |
Extra user data to pass to runInstance. |
Availability Zone |
The Availability Zone you want to launch the instance into. (Required) |
Subnet Id |
The ID of the subnet to launch the instance(s) into (for use with VPCs) |
Private IP |
The primary IP address. You must specify a value from the IP address range of the subnet. If no value is entered, an IP address from the IP address range of the subnet is selected to use with theVPCs. |
Use Private IP for subnet? |
If selected, a private IP address is used to create the resource. |
Instance Initiated Shutdown Behavior |
Specify the instance behaviour when an OS-level shutdown is performed. The instance can be either terminated or shut down. |
Tenancy |
Each instance that you launch into a VPC has a tenancy attribute. This attribute has the following values: default - Your instance runs on shared hardware. dedicated - Your instance runs on single-tenant hardware. host - Your instance runs on a Dedicated Host, which is an isolated server with configurations that you can control. |
IAM Profile Name |
Specify an IAM profile you want this instance to be associated with. If this parameter is not specified, instance will not be associated with a profile. |
Resource Pool |
|
If you specify a resource poolName in res_poolName, this is the workspace that will be used when creating the resource. |
|
Resource port |
If you specify a resource poolName in res_poolName, this is the port that will be used when creating the resource. |
Updates one or more attribute values of an Instance. Where required the procedure can be used to update attribute values of multiple instances.
| Parameter | Description |
|---|---|
Configuration |
The name of the config which holds all the connection information. This must reference a valid existing configuration. (Required) |
Instance IDs |
Comma-separated list of Instance IDs to update, e.g. i-00901da83f8647e57. |
Security Group Id |
New security group to use for updated instances, e.g. sg-79894433. If this field is left empty, the security group will not be updated. |
Instance Type |
New instance type. Note: to update instance type, the instance must be stopped and started again. |
User Data |
Extra user data to pass to runInstance. Note: to update User Data, the instance will be stopped and started again. |
Instance Initiated Shutdown Behavior |
Specify the instance behaviour when an OS-level shutdown is performed. Instance can be either terminated or shut down. |
This procedure deploys an Amazon EBS-backed instance.
-
Go to the API_StartInstance procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Instance name |
The name of the EC2 instance to deploy. (Required) |
This procedure stops an Amazon EBS-backed instance. Data is not be lost when the instance stops.
-
Go to the API_StartInstance procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Instance id |
The ID of the Amazon EC2 instance to stop. (Required) |
This procedure terminate one instance. When the procedure terminates, any data added to the disk or any changes made to the disk will be lost.
-
Go to the API_TearDownResource procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. |
Resource Name |
The name of the cloud resource to tear down. This procedure works only on a resource that was created in a dynamic environment. (Required) |
This procedure terminate one or more instances. When the procedures terminates any data added to the disk or any changes made to the disk will be lost.
-
Go to the API_Terminate procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Instance |
Reservation Id |
If parameter value is an instance ID, terminate the specific instance. If it is a reservation ID, terminate all the instances in the reservation. (Required) |
List of Resources |
This procedure allows this plugin to work with CloudManager plugin. CloudManager runs this procedure to add servers and calls the EC2 Auto Deploy procedure.
-
Go to the CloudManagerGrow procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of the configuration with all the EC-EC2 connection information. (Required) |
Security Group |
The EC2 security group for the new
instances. The default is |
Image Name |
The AMI or EMI image to use. (Required) |
Device |
The OS device to which the snapshot is connected when a snapshot is specified. |
Instance Type |
The EC2 instance type to create. The
default is
|
User Data |
Data to pass to the instance. |
Snapshot |
An Amazon EC2 snapshot. If a snapshot is specified, a new volume is created from the snapshot and attached to the running instance. |
Zone |
The Availability Zone where the
instance is launched. The default is |
Resource Pool |
Pool name for resources. (Required) |
Number of new instances |
The number of new servers. (Required) |
This procedure allows the plugin to work with CloudManager plugin. CloudManager runs this procedure to remove servers and calls the EC2 Auto Cleanup procedure.
-
Go to the CloudManagerShrink procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
List of Deployments |
A list of deployments (previously created by the CloudManagerGrow procedure) to stop. (Required) |
This procedure allows the plugin to work with CloudManager plugin. CloudManager runs this procedure to synchronize the servers.
-
Go to the CloudManagerSync procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
List of Deployments |
A list of deployments. (Required) |
This procedure cleans up the instances created with the "EC2 Auto Deploy" procedure. It uses the API_DeleteKey, API_Terminate, and API_DeleteVolume procedures to delete the key pair, storage, Elastic IP, and security settings.
-
Go to the EC2 Auto Cleanup procedure.
-
Enter the following parameters:
| Parameter | Description = |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Key name |
Name of the key pair to delete. (Required) |
Reservation Id |
The reservation ID. All instances in the reservation will be deleted. (Required). |
List of Volumes |
The names of volumes to delete. The volumne IDs are separated by semi-colons. |
List of Resources |
This procedure depoy new EC2 instances. It calls the API_CreateKey, API_RunInstances, ProcessVolumes, and API_AttachVolumes procedures to automatically create and associate the key pair, storage, Elastic IP, and security settings.
-
Go to the EC2 Auto Deploy procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Cleanup tag |
A key used to match a cleanup step to
the corresponding provision step. This allows recursive, multiple, or
both recursive and multiple calls calls within a procedure. The default
is |
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Number of Instances |
The number of instances to automatically deploy. (Required) |
EC2 AMI |
The name of the Amazon EC2 instance to deploy. (Required) |
Group |
The security group to use. The default
is |
Instance Type |
The instance type. The default is
|
Results Location |
Where to put the result. If the location is not specified, the result is only printed. (Required) |
Snapshot Id |
The ID of the snapshot for a volume and attached to the new instances. If the snapshot ID is not specified, volumes are not attached. |
User Data |
Extra user data to pass to the API_runInstances procedure. |
Volume device |
The device name of a volume attached to
an instance. Examples are |
Zone |
The zone where the instance is created. (Required) |
Resource Pool |
Name of the resource pool. If you enter a name, a new resource is created and put in the pool. |
Name of the workspace where the resources are created. |
|
Resource port |
ID of the port to which the new resources are assigned. |
This procedure pauses a instance store-backed AMI. It disconnects the volumes, saves them, and terminates the instance. It works with the EC2 Auto Resume procedure, which starts a new instance and re-attaches the volumes.
-
Go to the EC2 Auto Pause procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
List of Instances |
The instances to terminate, which can be a reservation, a single instance, or a list of instances. (Required) |
List of Volumes |
The list of volumes to detach from instances. (Required) |
This procedure restarts an instance. After the EC2 Auto Pause procedure runs, it starts a new istance and re-attaches the saved volumes.
-
Go to the EC2 Auto Resume procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Cleanup tag |
A key used to match a cleanup step to
the corresponding provision step. This allows recursive, multiple, or
both recursive and multiple calls within a procedure. The default is
|
Configuration |
The name of a valid existing configuration wtih the connection information. (Required) |
Number of Instances |
The number of instances to restart. (Required) |
EC2 AMI |
The name of the EC2 instance to deploy. (Required) |
Group |
The security group to use. The default
is |
Instance Type |
The instance type. The default is
|
Key name |
The name of the key pair to use. (Required) |
Results Location |
Where to put the result. If the
location is not specified, the result is only printed. The default is
|
Volume device |
The device name of a volume attached to
an instance. Examples are |
List of Volumes |
The list of volumes to attach to the new instances. (Required) |
Zone |
The zone where the instance is created.
The default is |
This procedure sets an instance name.
-
Go to the EC2 Set Name procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration wtih the connection information. (Required) |
Instance |
The ID of the instance. (Required) |
Name |
The new name of the instance. (Required) |
This procedure creates a new snapshot from a volume attached to an instance. It only creates a snapshot from the first volume found.
| Parameter | Description |
|---|---|
Configuration |
The name of a valid existing configuration with the connection information. (Required) |
Instance Id |
The ID of the running EC2 instance. (Required) |
Results Location |
Where to put the result. If the location is not specified, the result is only printed. (Required) |
Volume Id |
The ID of the volume. If you enter a list of volume IDs, separate the IDs with semi-colons. (Required) |
-
Create a plugin configuration.
-
Deploy an instance in EC2.
-
Create a key pair.
-
Run the instance.
-
Create a new volume from an snapshot.
-
Attach the volume to an instance.
-
Create a resource for this instance.
-
Run an operation using the resource.
-
Delete the key pair.
-
Delete the resource.
-
Delete the deployed instance.
-
Delete volume.
After the configuration is created, you can see it in "EC2 Configurations".
Go to the EC2 Auto Deploy procedure, enter the values from your EC2 server in the parameter fields:
This procedure calls the API_CreateKey, API_RunInstances, API_Run and API_AttachVolumes procedures to deploy the instance.
Create a new command step for the resource. In this example, get a resource from the resource pool and add an ec-perl sleep command for 30 seconds
After the resource is used, create a step using the EC2 Auto Cleanup procedure and enter the parameters:
This procedure calls the API_DeleteKey, API_Terminate and API_DeleteVolume procedures to clean up the instance.
After the job runs, you can see properties in the results location that you specified.
The following output appears during the Deploy procedures:
The following output appears during the Cleanup procedures:
HTTP Proxy functionality introduced in 2.5.0 will have the following UI limitations for customers who want to use this functionality:
- On CloudBees CD/RO (Flow) version 8.3, Proxy credentials will not appear in Resource Template UI and hence cannot be used to override what is defined already in Configuration. Other than this minor limitation, HTTP proxy will be completely functional.
- On CloudBees CD/RO (Flow) versions 8.2 and prior, Resource Template UI cannot be used to specify HTTP Proxy information and hence cannot create working Resource templates using this UI. However, the workaround for this use case would be to use DSL to create the Resource Templates.
- The documentation has been moved to the main documentation site.
- Upgrading certain third-party dependencies to address security issues.
- Renaming to "CloudBees CD/RO".
- Provisioning of Binary Dependencies (for example Grape jars) in the agent resource, required by this plugin, is now delivered through a newly introduced mechanism called Plugin Dependency Management. Binary dependencies will now be seamlessly delivered to the agent resource from the Flow Server, any time a new version of a plugin is invoked the first time. Flow Repository set up is no longer required for this plugin.
IAM Profile Nameparameter has been added to API_RunInstances procedure.
- Renaming "CloudBees".
- Configurations can be created by users with
@sign in a name.
-
Proxy credentials are now removed when configuration is deleted.
-
Logo icon has been added.
- Updated list of available instances.
-
Support for HTTP Proxy has been provided. Customers who use HTTP proxy can specify Proxy Information (Host, Port and Credentials at the configuration level) and all procedures will use the Proxy as second credentials for authentication. Proxy support will address both use cases of Procedure Invocation:
-
Direct Invocation
-
Invocation through Resource Templates.
-
For versions prior to 8.4 there are certain limitations with Proxy support for Resource Templates, using the Resource Template UI. Please refer to the Known Issues Section for details.
- A new procedure called API_UpdateInstances has been introduced that can be used to perform the following:
- Update one or more attribute values of an Instance.
- Update attribute values of multiple instances.
Note: The plugin has been packaged with new dependencies to address the API_UpdateInstances functionality. To promote the plugin the following steps need to be taken:
- Configure the Flow Repository Server and have it up and running.
- If plugin is promoted using
ectoo, and not from the platform UI, make sure that the flow repository server is visible to the instance from whichectoolis invoked.
-
Configured the plugin to allow the ElectricFlow UI to create configs inline of procedure form.
-
Configured the plugin to allow the ElectricFlow UI to render the plugin procedure parameters entirely using the configured form XMLs.
-
Enabled the plugin for managing the plugin configurations in-line when defining an application process step or a pipeline stage task.
-
Default value for
Tenancyfield has been removed (this fixes a problem with incompatible subnetId and groupName). -
In 2.4.0 (which is part of the 8.3 Release of Electric Flow), the
Tenancyfield was introduced by implementing the latest version of the AWS API. However, this version of the plugin can error if both Security Group and Subnet ID are both chosen in the plugin procedures, as AWS does not allow specifying both of them in their newer version. The current version fixes this issue. The following is the behavior of the plugin based on the value chosen for theTenancyfield in conjunction with Subnet ID and Security Group:-
no value chosen: Subnet ID and Security Group can be both chosen. -
default: Security Group and Subnet ID are both optional. If they are used only one of them can be specified. -
dedicated: Subnet ID is mandatory. Security Group is optional. Only one of them can be specified. -
host: Subnet ID is mandatory. Security Group is optional. Only one of them can be specified.
-
Tenancyparameter has been added to RunInstances procedure.
- Support of AWS Signature Version 4 has been added.
-
Added the ability to create a resource in non-default zone.
-
Added validation to the CreateConfiguration procedure for the dynamic environments feature.
-
Make instances parameter optional for API_DescribeInstances procedure.
-
Added check for instances and subnet’s IP limits before spinning instances in API_RunInstances procedure, minor changes.
-
Make
resource\_zoneparameter optional with default value default in API_RunInstances.
- Fixed issue with configurations being cached for Internet Explorer(R).
-
Added API_CreateVPC procedure.
-
Added API_CreateSubnet procedure.
-
Added API_DeleteVPC procedure.
-
Added Private IP and Instance Initiated Shutdown Behaviour parameters to API_RunInstance procedure.
-
Modified of API_Terminate procedure. Changed the behaviour of the procedure to wait till all instances get terminated in
reservation/instancelist.
-
Fixed the issue where the API_CreateTags procedure is visible from step picker. Default value for tag was set as
Name. -
Added properties in the
ec\_cloudprovisioning\_pluginproperty sheet for ElectricFlow Deploy. -
Propagated the summary property to the upper level.
-
Add VPC support to the API_RunInstances procedures.
-
Updated the Configuration page UI.
-
Removed Eucalyptus support from the plugin.
-
Fixed the Secret access key in the log.
-
Changed the Configuration Management procedure.
-
Added a new parameter called Attempt Connection? in the CreateConfiguration procedure.
-
Added a step called AttemptConnection in the CreateConfiguration procedure.
- Changed the procedure names in the step picker list.
-
Fixed the plugin configuration descriptions in the Help page.
-
Changed the Eucalyptus tool description.
- Fixed the problem with attached credentials.
- Fixed the DescribeInstances procedure (it returned fake data when non-existent instance was specified).
- Fixed the system test and API_DeleteVolume procedures.
- Improved the error handling.
-
Removed the CloudManagerGrow and CloudManagerShrink procedures from step picker.
-
Changed the style of the Help page.
-
Added a link to each procedure.
-
Cleaned up the parameter panel XML file.
-
Applied the new Help page template.
-
Added a detailed use case.
-
Added the new XML parameter panel to all procedures.
-
Fixed image parameter label on the API_RunInstances procedure.
- Updated the Help page.