You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.
Class: Aws::DataPipeline::Client
- Inherits:
-
Seahorse::Client::Base
- Object
- Seahorse::Client::Base
- Aws::DataPipeline::Client
- Defined in:
- (unknown)
Overview
An API client for AWS Data Pipeline. To construct a client, you need to configure a :region
and :credentials
.
datapipeline = Aws::DataPipeline::Client.new(
region: region_name,
credentials: credentials,
# ...
)
See #initialize for a full list of supported configuration options.
Region
You can configure a default region in the following locations:
ENV['AWS_REGION']
Aws.config[:region]
Go here for a list of supported regions.
Credentials
Default credentials are loaded automatically from the following locations:
ENV['AWS_ACCESS_KEY_ID']
andENV['AWS_SECRET_ACCESS_KEY']
Aws.config[:credentials]
- The shared credentials ini file at
~/.aws/credentials
(more information) - From an instance profile when running on EC2
You can also construct a credentials object from one of the following classes:
Alternatively, you configure credentials with :access_key_id
and
:secret_access_key
:
# load credentials from disk
creds = YAML.load(File.read('/path/to/secrets'))
Aws::DataPipeline::Client.new(
access_key_id: creds['access_key_id'],
secret_access_key: creds['secret_access_key']
)
Always load your credentials from outside your application. Avoid configuring credentials statically and never commit them to source control.
Attribute Summary collapse
Instance Attribute Summary
Attributes inherited from Seahorse::Client::Base
Constructor collapse
-
#initialize(options = {}) ⇒ Aws::DataPipeline::Client
constructor
Constructs an API client.
API Operations collapse
-
#activate_pipeline(options = {}) ⇒ Struct
Validates the specified pipeline and starts processing pipeline tasks.
-
#add_tags(options = {}) ⇒ Struct
Adds or modifies tags for the specified pipeline.
.
-
#create_pipeline(options = {}) ⇒ Types::CreatePipelineOutput
Creates a new, empty pipeline.
-
#deactivate_pipeline(options = {}) ⇒ Struct
Deactivates the specified running pipeline.
-
#delete_pipeline(options = {}) ⇒ Struct
Deletes a pipeline, its pipeline definition, and its run history.
-
#describe_objects(options = {}) ⇒ Types::DescribeObjectsOutput
Gets the object definitions for a set of objects associated with the pipeline.
-
#describe_pipelines(options = {}) ⇒ Types::DescribePipelinesOutput
Retrieves metadata about one or more pipelines.
-
#evaluate_expression(options = {}) ⇒ Types::EvaluateExpressionOutput
Task runners call
EvaluateExpression
to evaluate a string in the context of the specified object. -
#get_pipeline_definition(options = {}) ⇒ Types::GetPipelineDefinitionOutput
Gets the definition of the specified pipeline.
-
#list_pipelines(options = {}) ⇒ Types::ListPipelinesOutput
Lists the pipeline identifiers for all active pipelines that you have permission to access.
.
-
#poll_for_task(options = {}) ⇒ Types::PollForTaskOutput
Task runners call
PollForTask
to receive a task to perform from AWS Data Pipeline. -
#put_pipeline_definition(options = {}) ⇒ Types::PutPipelineDefinitionOutput
Adds tasks, schedules, and preconditions to the specified pipeline.
-
#query_objects(options = {}) ⇒ Types::QueryObjectsOutput
Queries the specified pipeline for the names of objects that match the specified set of conditions.
.
-
#remove_tags(options = {}) ⇒ Struct
Removes existing tags from the specified pipeline.
.
-
#report_task_progress(options = {}) ⇒ Types::ReportTaskProgressOutput
Task runners call
ReportTaskProgress
when assigned a task to acknowledge that it has the task. -
#report_task_runner_heartbeat(options = {}) ⇒ Types::ReportTaskRunnerHeartbeatOutput
Task runners call
ReportTaskRunnerHeartbeat
every 15 minutes to indicate that they are operational. -
#set_status(options = {}) ⇒ Struct
Requests that the status of the specified physical or logical pipeline objects be updated in the specified pipeline.
-
#set_task_status(options = {}) ⇒ Struct
Task runners call
SetTaskStatus
to notify AWS Data Pipeline that a task is completed and provide information about the final status. -
#validate_pipeline_definition(options = {}) ⇒ Types::ValidatePipelineDefinitionOutput
Validates the specified pipeline definition to ensure that it is well formed and can be run without error.
.
Instance Method Summary collapse
-
#wait_until(waiter_name, params = {}) {|waiter| ... } ⇒ Boolean
Waiters polls an API operation until a resource enters a desired state.
-
#waiter_names ⇒ Array<Symbol>
Returns the list of supported waiters.
Methods inherited from Seahorse::Client::Base
add_plugin, api, #build_request, clear_plugins, define, new, #operation, #operation_names, plugins, remove_plugin, set_api, set_plugins
Methods included from Seahorse::Client::HandlerBuilder
#handle, #handle_request, #handle_response
Constructor Details
#initialize(options = {}) ⇒ Aws::DataPipeline::Client
Constructs an API client.
Instance Method Details
#activate_pipeline(options = {}) ⇒ Struct
Validates the specified pipeline and starts processing pipeline tasks. If the pipeline does not pass validation, activation fails.
If you need to pause the pipeline to investigate an issue with a component, such as a data source or script, call DeactivatePipeline.
To activate a finished pipeline, modify the end date for the pipeline and then activate it.
#add_tags(options = {}) ⇒ Struct
Adds or modifies tags for the specified pipeline.
#create_pipeline(options = {}) ⇒ Types::CreatePipelineOutput
Creates a new, empty pipeline. Use PutPipelineDefinition to populate the pipeline.
#deactivate_pipeline(options = {}) ⇒ Struct
Deactivates the specified running pipeline. The pipeline is set to the DEACTIVATING
state until the deactivation process completes.
To resume a deactivated pipeline, use ActivatePipeline. By default, the pipeline resumes from the last completed execution. Optionally, you can specify the date and time to resume the pipeline.
#delete_pipeline(options = {}) ⇒ Struct
Deletes a pipeline, its pipeline definition, and its run history. AWS Data Pipeline attempts to cancel instances associated with the pipeline that are currently being processed by task runners.
Deleting a pipeline cannot be undone. You cannot query or restore a deleted pipeline. To temporarily pause a pipeline instead of deleting it, call SetStatus with the status set to PAUSE
on individual components. Components that are paused by SetStatus can be resumed.
#describe_objects(options = {}) ⇒ Types::DescribeObjectsOutput
Gets the object definitions for a set of objects associated with the pipeline. Object definitions are composed of a set of fields that define the properties of the object.
#describe_pipelines(options = {}) ⇒ Types::DescribePipelinesOutput
Retrieves metadata about one or more pipelines. The information retrieved includes the name of the pipeline, the pipeline identifier, its current state, and the user account that owns the pipeline. Using account credentials, you can retrieve metadata about pipelines that you or your IAM users have created. If you are using an IAM user account, you can retrieve metadata about only those pipelines for which you have read permissions.
To retrieve the full pipeline definition instead of metadata about the pipeline, call GetPipelineDefinition.
#evaluate_expression(options = {}) ⇒ Types::EvaluateExpressionOutput
Task runners call EvaluateExpression
to evaluate a string in the context of the specified object. For example, a task runner can evaluate SQL queries stored in Amazon S3.
#get_pipeline_definition(options = {}) ⇒ Types::GetPipelineDefinitionOutput
Gets the definition of the specified pipeline. You can call GetPipelineDefinition
to retrieve the pipeline definition that you provided using PutPipelineDefinition.
#list_pipelines(options = {}) ⇒ Types::ListPipelinesOutput
Lists the pipeline identifiers for all active pipelines that you have permission to access.
#poll_for_task(options = {}) ⇒ Types::PollForTaskOutput
Task runners call PollForTask
to receive a task to perform from AWS Data Pipeline. The task runner specifies which tasks it can perform by setting a value for the workerGroup
parameter. The task returned can come from any of the pipelines that match the workerGroup
value passed in by the task runner and that was launched using the IAM user credentials specified by the task runner.
If tasks are ready in the work queue, PollForTask
returns a response immediately. If no tasks are available in the queue, PollForTask
uses long-polling and holds on to a poll connection for up to a 90 seconds, during which time the first newly scheduled task is handed to the task runner. To accomodate this, set the socket timeout in your task runner to 90 seconds. The task runner should not call PollForTask
again on the same workerGroup
until it receives a response, and this can take up to 90 seconds.
#put_pipeline_definition(options = {}) ⇒ Types::PutPipelineDefinitionOutput
Adds tasks, schedules, and preconditions to the specified pipeline. You can use PutPipelineDefinition
to populate a new pipeline.
PutPipelineDefinition
also validates the configuration as it adds it to the pipeline. Changes to the pipeline are saved unless one of the following three validation errors exists in the pipeline.
- An object is missing a name or identifier field.
- A string or reference field is empty.
- The number of objects in the pipeline exceeds the maximum allowed objects.
- The pipeline is in a FINISHED state.
Pipeline object definitions are passed to the PutPipelineDefinition
action and returned by the GetPipelineDefinition action.
#query_objects(options = {}) ⇒ Types::QueryObjectsOutput
Queries the specified pipeline for the names of objects that match the specified set of conditions.
#remove_tags(options = {}) ⇒ Struct
Removes existing tags from the specified pipeline.
#report_task_progress(options = {}) ⇒ Types::ReportTaskProgressOutput
Task runners call ReportTaskProgress
when assigned a task to acknowledge that it has the task. If the web service does not receive this acknowledgement within 2 minutes, it assigns the task in a subsequent PollForTask call. After this initial acknowledgement, the task runner only needs to report progress every 15 minutes to maintain its ownership of the task. You can change this reporting time from 15 minutes by specifying a reportProgressTimeout
field in your pipeline.
If a task runner does not report its status after 5 minutes, AWS Data Pipeline assumes that the task runner is unable to process the task and reassigns the task in a subsequent response to PollForTask. Task runners should call ReportTaskProgress
every 60 seconds.
#report_task_runner_heartbeat(options = {}) ⇒ Types::ReportTaskRunnerHeartbeatOutput
Task runners call ReportTaskRunnerHeartbeat
every 15 minutes to indicate that they are operational. If the AWS Data Pipeline Task Runner is launched on a resource managed by AWS Data Pipeline, the web service can use this call to detect when the task runner application has failed and restart a new instance.
#set_status(options = {}) ⇒ Struct
Requests that the status of the specified physical or logical pipeline objects be updated in the specified pipeline. This update might not occur immediately, but is eventually consistent. The status that can be set depends on the type of object (for example, DataNode or Activity). You cannot perform this operation on FINISHED
pipelines and attempting to do so returns InvalidRequestException
.
#set_task_status(options = {}) ⇒ Struct
Task runners call SetTaskStatus
to notify AWS Data Pipeline that a task is completed and provide information about the final status. A task runner makes this call regardless of whether the task was sucessful. A task runner does not need to call SetTaskStatus
for tasks that are canceled by the web service during a call to ReportTaskProgress.
#validate_pipeline_definition(options = {}) ⇒ Types::ValidatePipelineDefinitionOutput
Validates the specified pipeline definition to ensure that it is well formed and can be run without error.
#wait_until(waiter_name, params = {}) {|waiter| ... } ⇒ Boolean
Waiters polls an API operation until a resource enters a desired state.
Basic Usage
Waiters will poll until they are succesful, they fail by entering a terminal state, or until a maximum number of attempts are made.
# polls in a loop, sleeping between attempts client.waiter_until(waiter_name, params)
Configuration
You can configure the maximum number of polling attempts, and the delay (in seconds) between each polling attempt. You configure waiters by passing a block to #wait_until:
# poll for ~25 seconds
client.wait_until(...) do |w|
w.max_attempts = 5
w.delay = 5
end
Callbacks
You can be notified before each polling attempt and before each
delay. If you throw :success
or :failure
from these callbacks,
it will terminate the waiter.
started_at = Time.now
client.wait_until(...) do |w|
# disable max attempts
w.max_attempts = nil
# poll for 1 hour, instead of a number of attempts
w.before_wait do |attempts, response|
throw :failure if Time.now - started_at > 3600
end
end
Handling Errors
When a waiter is successful, it returns true
. When a waiter
fails, it raises an error. All errors raised extend from
Waiters::Errors::WaiterFailed.
begin
client.wait_until(...)
rescue Aws::Waiters::Errors::WaiterFailed
# resource did not enter the desired state in time
end
#waiter_names ⇒ Array<Symbol>
Returns the list of supported waiters. The following table lists the supported waiters and the client method they call:
Waiter Name | Client Method | Default Delay: | Default Max Attempts: |
---|