#[non_exhaustive]pub struct UpdateAgreementInput {
pub agreement_id: Option<String>,
pub server_id: Option<String>,
pub description: Option<String>,
pub status: Option<AgreementStatusType>,
pub local_profile_id: Option<String>,
pub partner_profile_id: Option<String>,
pub base_directory: Option<String>,
pub access_role: Option<String>,
pub preserve_filename: Option<PreserveFilenameType>,
pub enforce_message_signing: Option<EnforceMessageSigningType>,
pub custom_directories: Option<CustomDirectoriesType>,
}
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.agreement_id: Option<String>
A unique identifier for the agreement. This identifier is returned when you create an agreement.
server_id: Option<String>
A system-assigned unique identifier for a server instance. This is the specific server that the agreement uses.
description: Option<String>
To replace the existing description, provide a short description for the agreement.
status: Option<AgreementStatusType>
You can update the status for the agreement, either activating an inactive agreement or the reverse.
local_profile_id: Option<String>
A unique identifier for the AS2 local profile.
To change the local profile identifier, provide a new value here.
partner_profile_id: Option<String>
A unique identifier for the partner profile. To change the partner profile identifier, provide a new value here.
base_directory: Option<String>
To change the landing directory (folder) for files that are transferred, provide the bucket folder that you want to use; for example, /amzn-s3-demo-bucket/home/mydirectory
.
access_role: Option<String>
Connectors are used to send files using either the AS2 or SFTP protocol. For the access role, provide the Amazon Resource Name (ARN) of the Identity and Access Management role to use.
For AS2 connectors
With AS2, you can send files by calling StartFileTransfer
and specifying the file paths in the request parameter, SendFilePaths
. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt
, parent directory is /bucket/dir/
) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole
needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer
request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer
.
If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue
permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt
permission for that key.
For SFTP connectors
Make sure that the access role provides read and write access to the parent directory of the file location that's used in the StartFileTransfer
request. Additionally, make sure that the role provides secretsmanager:GetSecretValue
permission to Secrets Manager.
preserve_filename: Option<PreserveFilenameType>
Determines whether or not Transfer Family appends a unique string of characters to the end of the AS2 message payload filename when saving it.
-
ENABLED
: the filename provided by your trading parter is preserved when the file is saved. -
DISABLED
(default value): when Transfer Family saves the file, the filename is adjusted, as described in File names and locations.
enforce_message_signing: Option<EnforceMessageSigningType>
Determines whether or not unsigned messages from your trading partners will be accepted.
-
ENABLED
: Transfer Family rejects unsigned messages from your trading partner. -
DISABLED
(default value): Transfer Family accepts unsigned messages from your trading partner.
custom_directories: Option<CustomDirectoriesType>
A CustomDirectoriesType
structure. This structure specifies custom directories for storing various AS2 message files. You can specify directories for the following types of files.
-
Failed files
-
MDN files
-
Payload files
-
Status files
-
Temporary files
Implementations§
Source§impl UpdateAgreementInput
impl UpdateAgreementInput
Sourcepub fn agreement_id(&self) -> Option<&str>
pub fn agreement_id(&self) -> Option<&str>
A unique identifier for the agreement. This identifier is returned when you create an agreement.
Sourcepub fn server_id(&self) -> Option<&str>
pub fn server_id(&self) -> Option<&str>
A system-assigned unique identifier for a server instance. This is the specific server that the agreement uses.
Sourcepub fn description(&self) -> Option<&str>
pub fn description(&self) -> Option<&str>
To replace the existing description, provide a short description for the agreement.
Sourcepub fn status(&self) -> Option<&AgreementStatusType>
pub fn status(&self) -> Option<&AgreementStatusType>
You can update the status for the agreement, either activating an inactive agreement or the reverse.
Sourcepub fn local_profile_id(&self) -> Option<&str>
pub fn local_profile_id(&self) -> Option<&str>
A unique identifier for the AS2 local profile.
To change the local profile identifier, provide a new value here.
Sourcepub fn partner_profile_id(&self) -> Option<&str>
pub fn partner_profile_id(&self) -> Option<&str>
A unique identifier for the partner profile. To change the partner profile identifier, provide a new value here.
Sourcepub fn base_directory(&self) -> Option<&str>
pub fn base_directory(&self) -> Option<&str>
To change the landing directory (folder) for files that are transferred, provide the bucket folder that you want to use; for example, /amzn-s3-demo-bucket/home/mydirectory
.
Sourcepub fn access_role(&self) -> Option<&str>
pub fn access_role(&self) -> Option<&str>
Connectors are used to send files using either the AS2 or SFTP protocol. For the access role, provide the Amazon Resource Name (ARN) of the Identity and Access Management role to use.
For AS2 connectors
With AS2, you can send files by calling StartFileTransfer
and specifying the file paths in the request parameter, SendFilePaths
. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt
, parent directory is /bucket/dir/
) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole
needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer
request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer
.
If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue
permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt
permission for that key.
For SFTP connectors
Make sure that the access role provides read and write access to the parent directory of the file location that's used in the StartFileTransfer
request. Additionally, make sure that the role provides secretsmanager:GetSecretValue
permission to Secrets Manager.
Sourcepub fn preserve_filename(&self) -> Option<&PreserveFilenameType>
pub fn preserve_filename(&self) -> Option<&PreserveFilenameType>
Determines whether or not Transfer Family appends a unique string of characters to the end of the AS2 message payload filename when saving it.
-
ENABLED
: the filename provided by your trading parter is preserved when the file is saved. -
DISABLED
(default value): when Transfer Family saves the file, the filename is adjusted, as described in File names and locations.
Sourcepub fn enforce_message_signing(&self) -> Option<&EnforceMessageSigningType>
pub fn enforce_message_signing(&self) -> Option<&EnforceMessageSigningType>
Determines whether or not unsigned messages from your trading partners will be accepted.
-
ENABLED
: Transfer Family rejects unsigned messages from your trading partner. -
DISABLED
(default value): Transfer Family accepts unsigned messages from your trading partner.
Sourcepub fn custom_directories(&self) -> Option<&CustomDirectoriesType>
pub fn custom_directories(&self) -> Option<&CustomDirectoriesType>
A CustomDirectoriesType
structure. This structure specifies custom directories for storing various AS2 message files. You can specify directories for the following types of files.
-
Failed files
-
MDN files
-
Payload files
-
Status files
-
Temporary files
Source§impl UpdateAgreementInput
impl UpdateAgreementInput
Sourcepub fn builder() -> UpdateAgreementInputBuilder
pub fn builder() -> UpdateAgreementInputBuilder
Creates a new builder-style object to manufacture UpdateAgreementInput
.
Trait Implementations§
Source§impl Clone for UpdateAgreementInput
impl Clone for UpdateAgreementInput
Source§fn clone(&self) -> UpdateAgreementInput
fn clone(&self) -> UpdateAgreementInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for UpdateAgreementInput
impl Debug for UpdateAgreementInput
Source§impl PartialEq for UpdateAgreementInput
impl PartialEq for UpdateAgreementInput
impl StructuralPartialEq for UpdateAgreementInput
Auto Trait Implementations§
impl Freeze for UpdateAgreementInput
impl RefUnwindSafe for UpdateAgreementInput
impl Send for UpdateAgreementInput
impl Sync for UpdateAgreementInput
impl Unpin for UpdateAgreementInput
impl UnwindSafe for UpdateAgreementInput
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);