Plugin procedures can be used in procedure steps, process steps, and pipeline tasks, allowing you to orchestrate third-party tools at the appropriate time in your component, application process, or pipeline.
Depending on your plugin configuration and how you run procedures, the Differences in plugin UI behavior. field may behave differently in the CloudBees CD/RO UI. For more information, refer to |
CreateLambdaFunction
Creates AWS Lambda functions using the AWS SDK. For more information about AWS Lambda functions, visit the AWS Lambda Console.
Input parameters
Parameter | Description |
---|---|
Configuration name |
Required. The previously defined configuration for the plugin. |
Function name |
Required. AWS Lambda function name to create. |
Runtime name |
Required. Runtime name for the Lambda function. For example, |
Path to deployment package archive |
Required. Archive file with the Lambda function code. May be created manually or exported from the AWS Lambda console. |
Lambda handler |
Required. Handler to use to invoke the Lambda function invocation. For example, if your archive file is |
AWS role |
Required. Amazon Resource Name (ARN) of the AWS role to use for AWS Lambda execution. This role must have sufficient permissions. |
RunLambdaFunction
Runs AWS Lambda functions.
Input parameters
Parameter | Description |
---|---|
Configuration name |
Required. The previously defined configuration for the plugin. |
Function name |
Required. AWS Lambda function name to create. For more information on AWS Lambda functions, visit the AWS Console. |
Function parameters |
Parameters in JSON format to pass to the AWS Lambda function. These parameters are available through event object. |
Success criteria |
Required. Procedure result returned by the Lambda function to indicate success status. If Is regex? is selected, this value is treated as a regular expression. |
Is regex? |
If selected, the Success criteria field is treated as a regular expression. |