pub struct Client { /* private fields */ }Expand description
Client for AWS IoT Jobs Data Plane
Client for invoking operations on AWS IoT Jobs Data Plane. Each operation on AWS IoT Jobs Data Plane is a method on this
this struct. .send() MUST be invoked on the generated operations to dispatch the request to the service.
§Constructing a Client
A Config is required to construct a client. For most use cases, the aws-config
crate should be used to automatically resolve this config using
aws_config::load_from_env(), since this will resolve an SdkConfig which can be shared
across multiple different AWS SDK clients. This config resolution process can be customized
by calling aws_config::from_env() instead, which returns a ConfigLoader that uses
the builder pattern to customize the default config.
In the simplest case, creating a client looks as follows:
let config = aws_config::load_from_env().await;
let client = aws_sdk_iotjobsdataplane::Client::new(&config);Occasionally, SDKs may have additional service-specific values that can be set on the Config that
is absent from SdkConfig, or slightly different settings for a specific client may be desired.
The Builder struct implements From<&SdkConfig>, so setting these specific settings can be
done as follows:
let sdk_config = ::aws_config::load_from_env().await;
let config = aws_sdk_iotjobsdataplane::config::Builder::from(&sdk_config)
.some_service_specific_setting("value")
.build();See the aws-config docs and Config for more information on customizing configuration.
Note: Client construction is expensive due to connection thread pool initialization, and should be done once at application start-up.
§Using the Client
A client has a function for every operation that can be performed by the service.
For example, the DescribeJobExecution operation has
a Client::describe_job_execution, function which returns a builder for that operation.
The fluent builder ultimately has a send() function that returns an async future that
returns a result, as illustrated below:
let result = client.describe_job_execution()
.job_id("example")
.send()
.await;The underlying HTTP requests that get made by this can be modified with the customize_operation
function on the fluent builder. See the customize module for more
information.
Implementations§
Source§impl Client
impl Client
Sourcepub fn describe_job_execution(&self) -> DescribeJobExecutionFluentBuilder
pub fn describe_job_execution(&self) -> DescribeJobExecutionFluentBuilder
Constructs a fluent builder for the DescribeJobExecution operation.
- The fluent builder is configurable:
job_id(impl Into<String>)/set_job_id(Option<String>):
required: trueThe unique identifier assigned to this job when it was created.
thing_name(impl Into<String>)/set_thing_name(Option<String>):
required: trueThe thing name associated with the device the job execution is running on.
include_job_document(bool)/set_include_job_document(Option<bool>):
required: falseOptional. Unless set to false, the response contains the job document. The default is true.
execution_number(i64)/set_execution_number(Option<i64>):
required: falseOptional. A number that identifies a particular job execution on a particular device. If not specified, the latest job execution is returned.
- On success, responds with
DescribeJobExecutionOutputwith field(s):execution(Option<JobExecution>):Contains data about a job execution.
- On failure, responds with
SdkError<DescribeJobExecutionError>
Source§impl Client
impl Client
Sourcepub fn get_pending_job_executions(&self) -> GetPendingJobExecutionsFluentBuilder
pub fn get_pending_job_executions(&self) -> GetPendingJobExecutionsFluentBuilder
Constructs a fluent builder for the GetPendingJobExecutions operation.
- The fluent builder is configurable:
thing_name(impl Into<String>)/set_thing_name(Option<String>):
required: trueThe name of the thing that is executing the job.
- On success, responds with
GetPendingJobExecutionsOutputwith field(s):in_progress_jobs(Option<Vec::<JobExecutionSummary>>):A list of JobExecutionSummary objects with status IN_PROGRESS.
queued_jobs(Option<Vec::<JobExecutionSummary>>):A list of JobExecutionSummary objects with status QUEUED.
- On failure, responds with
SdkError<GetPendingJobExecutionsError>
Source§impl Client
impl Client
Sourcepub fn start_command_execution(&self) -> StartCommandExecutionFluentBuilder
pub fn start_command_execution(&self) -> StartCommandExecutionFluentBuilder
Constructs a fluent builder for the StartCommandExecution operation.
- The fluent builder is configurable:
target_arn(impl Into<String>)/set_target_arn(Option<String>):
required: trueThe Amazon Resource Number (ARN) of the device where the command execution is occurring.
command_arn(impl Into<String>)/set_command_arn(Option<String>):
required: trueThe Amazon Resource Number (ARN) of the command. For example,
arn:aws:iot:: :command/ parameters(impl Into<String>, CommandParameterValue)/set_parameters(Option<HashMap::<String, CommandParameterValue>>):
required: falseA list of parameters that are required by the
StartCommandExecutionAPI when performing the command on a device.execution_timeout_seconds(i64)/set_execution_timeout_seconds(Option<i64>):
required: falseSpecifies the amount of time in second the device has to finish the command execution. A timer is started as soon as the command execution is created. If the command execution status is not set to another terminal state before the timer expires, it will automatically update to
TIMED_OUT.client_token(impl Into<String>)/set_client_token(Option<String>):
required: falseThe client token is used to implement idempotency. It ensures that the request completes no more than one time. If you retry a request with the same token and the same parameters, the request will complete successfully. However, if you retry the request using the same token but different parameters, an HTTP 409 conflict occurs. If you omit this value, Amazon Web Services SDKs will automatically generate a unique client request.
- On success, responds with
StartCommandExecutionOutputwith field(s):execution_id(Option<String>):A unique identifier for the command execution.
- On failure, responds with
SdkError<StartCommandExecutionError>
Source§impl Client
impl Client
Sourcepub fn start_next_pending_job_execution(
&self,
) -> StartNextPendingJobExecutionFluentBuilder
pub fn start_next_pending_job_execution( &self, ) -> StartNextPendingJobExecutionFluentBuilder
Constructs a fluent builder for the StartNextPendingJobExecution operation.
- The fluent builder is configurable:
thing_name(impl Into<String>)/set_thing_name(Option<String>):
required: trueThe name of the thing associated with the device.
status_details(impl Into<String>, impl Into<String>)/set_status_details(Option<HashMap::<String, String>>):
required: falseA collection of name/value pairs that describe the status of the job execution. If not specified, the statusDetails are unchanged.
The maximum length of the value in the name/value pair is 1,024 characters.
step_timeout_in_minutes(i64)/set_step_timeout_in_minutes(Option<i64>):
required: falseSpecifies the amount of time this device has to finish execution of this job. If the job execution status is not set to a terminal state before this timer expires, or before the timer is reset (by calling
UpdateJobExecution, setting the status toIN_PROGRESS, and specifying a new timeout value in fieldstepTimeoutInMinutes) the job execution status will be automatically set toTIMED_OUT. Note that setting the step timeout has no effect on the in progress timeout that may have been specified when the job was created (CreateJobusing fieldtimeoutConfig).Valid values for this parameter range from 1 to 10080 (1 minute to 7 days).
- On success, responds with
StartNextPendingJobExecutionOutputwith field(s):execution(Option<JobExecution>):A JobExecution object.
- On failure, responds with
SdkError<StartNextPendingJobExecutionError>
Source§impl Client
impl Client
Sourcepub fn update_job_execution(&self) -> UpdateJobExecutionFluentBuilder
pub fn update_job_execution(&self) -> UpdateJobExecutionFluentBuilder
Constructs a fluent builder for the UpdateJobExecution operation.
- The fluent builder is configurable:
job_id(impl Into<String>)/set_job_id(Option<String>):
required: trueThe unique identifier assigned to this job when it was created.
thing_name(impl Into<String>)/set_thing_name(Option<String>):
required: trueThe name of the thing associated with the device.
status(JobExecutionStatus)/set_status(Option<JobExecutionStatus>):
required: trueThe new status for the job execution (IN_PROGRESS, FAILED, SUCCESS, or REJECTED). This must be specified on every update.
status_details(impl Into<String>, impl Into<String>)/set_status_details(Option<HashMap::<String, String>>):
required: falseOptional. A collection of name/value pairs that describe the status of the job execution. If not specified, the statusDetails are unchanged.
The maximum length of the value in the name/value pair is 1,024 characters.
step_timeout_in_minutes(i64)/set_step_timeout_in_minutes(Option<i64>):
required: falseSpecifies the amount of time this device has to finish execution of this job. If the job execution status is not set to a terminal state before this timer expires, or before the timer is reset (by again calling
UpdateJobExecution, setting the status toIN_PROGRESS, and specifying a new timeout value in this field) the job execution status will be automatically set toTIMED_OUT. Note that setting or resetting the step timeout has no effect on the in progress timeout that may have been specified when the job was created (CreateJobusing fieldtimeoutConfig).Valid values for this parameter range from 1 to 10080 (1 minute to 7 days). A value of -1 is also valid and will cancel the current step timer (created by an earlier use of
UpdateJobExecutionRequest).expected_version(i64)/set_expected_version(Option<i64>):
required: falseOptional. The expected current version of the job execution. Each time you update the job execution, its version is incremented. If the version of the job execution stored in Jobs does not match, the update is rejected with a VersionMismatch error, and an ErrorResponse that contains the current job execution status data is returned. (This makes it unnecessary to perform a separate DescribeJobExecution request in order to obtain the job execution status data.)
include_job_execution_state(bool)/set_include_job_execution_state(Option<bool>):
required: falseOptional. When included and set to true, the response contains the JobExecutionState data. The default is false.
include_job_document(bool)/set_include_job_document(Option<bool>):
required: falseOptional. When set to true, the response contains the job document. The default is false.
execution_number(i64)/set_execution_number(Option<i64>):
required: falseOptional. A number that identifies a particular job execution on a particular device.
- On success, responds with
UpdateJobExecutionOutputwith field(s):execution_state(Option<JobExecutionState>):A JobExecutionState object.
job_document(Option<String>):The contents of the Job Documents.
- On failure, responds with
SdkError<UpdateJobExecutionError>
Source§impl Client
impl Client
Sourcepub fn from_conf(conf: Config) -> Self
pub fn from_conf(conf: Config) -> Self
Creates a new client from the service Config.
§Panics
This method will panic in the following cases:
- Retries or timeouts are enabled without a
sleep_implconfigured. - Identity caching is enabled without a
sleep_implandtime_sourceconfigured. - No
behavior_versionis provided.
The panic message for each of these will have instructions on how to resolve them.
Source§impl Client
impl Client
Sourcepub fn new(sdk_config: &SdkConfig) -> Self
pub fn new(sdk_config: &SdkConfig) -> Self
Creates a new client from an SDK Config.
§Panics
- This method will panic if the
sdk_configis missing an async sleep implementation. If you experience this panic, set thesleep_implon the Config passed into this function to fix it. - This method will panic if the
sdk_configis missing an HTTP connector. If you experience this panic, set thehttp_connectoron the Config passed into this function to fix it. - This method will panic if no
BehaviorVersionis provided. If you experience this panic, setbehavior_versionon the Config or enable thebehavior-version-latestCargo feature.
Trait Implementations§
Auto Trait Implementations§
impl Freeze for Client
impl !RefUnwindSafe for Client
impl Send for Client
impl Sync for Client
impl Unpin for Client
impl !UnwindSafe for Client
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self into a Left variant of Either<Self, Self>
if into_left is true.
Converts self into a Right variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self into a Left variant of Either<Self, Self>
if into_left(&self) returns true.
Converts self into a Right variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the foreground set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red() and
green(), which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg():
use yansi::{Paint, Color};
painted.fg(Color::White);Set foreground color to white using white().
use yansi::Paint;
painted.white();Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the background set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red() and
on_green(), which have the same functionality but
are pithier.
§Example
Set background color to red using fg():
use yansi::{Paint, Color};
painted.bg(Color::Red);Set background color to red using on_red().
use yansi::Paint;
painted.on_red();Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute value.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold() and
underline(), which have the same functionality
but are pithier.
§Example
Make text bold using attr():
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);Make text bold using using bold().
use yansi::Paint;
painted.bold();Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi Quirk value.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask() and
wrap(), which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk():
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);Enable wrapping using wrap().
use yansi::Paint;
painted.wrap();Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted only when both stdout and stderr are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);