Struct aws_sdk_qldb::operation::update_ledger_permissions_mode::builders::UpdateLedgerPermissionsModeInputBuilder

#[non_exhaustive]
pub struct UpdateLedgerPermissionsModeInputBuilder { /* private fields */ }

A builder for UpdateLedgerPermissionsModeInput.

Implementations

impl UpdateLedgerPermissionsModeInputBuilder

pub fn name(self, input: impl Into<String>) -> Self

The name of the ledger.

This field is required.

pub fn set_name(self, input: Option<String>) -> Self

The name of the ledger.

pub fn get_name(&self) -> &Option<String>

The name of the ledger.

pub fn permissions_mode(self, input: PermissionsMode) -> Self

The permissions mode to assign to the ledger. This parameter can have one of the following values:

• ALLOW_ALL: A legacy permissions mode that enables access control with API-level granularity for ledgers.

  This mode allows users who have the SendCommand API permission for this ledger to run all PartiQL commands (hence, ALLOW_ALL) on any tables in the specified ledger. This mode disregards any table-level or command-level IAM permissions policies that you create for the ledger.

• STANDARD: (Recommended) A permissions mode that enables access control with finer granularity for ledgers, tables, and PartiQL commands.

  By default, this mode denies all user requests to run any PartiQL commands on any tables in this ledger. To allow PartiQL commands to run, you must create IAM permissions policies for specific table resources and PartiQL actions, in addition to the SendCommand API permission for the ledger. For information, see Getting started with the standard permissions mode in the Amazon QLDB Developer Guide.

We strongly recommend using the STANDARD permissions mode to maximize the security of your ledger data.

This field is required.

pub fn set_permissions_mode(self, input: Option<PermissionsMode>) -> Self

The permissions mode to assign to the ledger. This parameter can have one of the following values:

• ALLOW_ALL: A legacy permissions mode that enables access control with API-level granularity for ledgers.

  This mode allows users who have the SendCommand API permission for this ledger to run all PartiQL commands (hence, ALLOW_ALL) on any tables in the specified ledger. This mode disregards any table-level or command-level IAM permissions policies that you create for the ledger.

• STANDARD: (Recommended) A permissions mode that enables access control with finer granularity for ledgers, tables, and PartiQL commands.

  By default, this mode denies all user requests to run any PartiQL commands on any tables in this ledger. To allow PartiQL commands to run, you must create IAM permissions policies for specific table resources and PartiQL actions, in addition to the SendCommand API permission for the ledger. For information, see Getting started with the standard permissions mode in the Amazon QLDB Developer Guide.

We strongly recommend using the STANDARD permissions mode to maximize the security of your ledger data.

pub fn get_permissions_mode(&self) -> &Option<PermissionsMode>

The permissions mode to assign to the ledger. This parameter can have one of the following values:

• ALLOW_ALL: A legacy permissions mode that enables access control with API-level granularity for ledgers.

  This mode allows users who have the SendCommand API permission for this ledger to run all PartiQL commands (hence, ALLOW_ALL) on any tables in the specified ledger. This mode disregards any table-level or command-level IAM permissions policies that you create for the ledger.

• STANDARD: (Recommended) A permissions mode that enables access control with finer granularity for ledgers, tables, and PartiQL commands.

  By default, this mode denies all user requests to run any PartiQL commands on any tables in this ledger. To allow PartiQL commands to run, you must create IAM permissions policies for specific table resources and PartiQL actions, in addition to the SendCommand API permission for the ledger. For information, see Getting started with the standard permissions mode in the Amazon QLDB Developer Guide.

We strongly recommend using the STANDARD permissions mode to maximize the security of your ledger data.

pub fn build(self) -> Result<UpdateLedgerPermissionsModeInput, BuildError>

Consumes the builder and constructs a UpdateLedgerPermissionsModeInput.

impl UpdateLedgerPermissionsModeInputBuilder

pub async fn send_with( self, client: &Client ) -> Result<UpdateLedgerPermissionsModeOutput, SdkError<UpdateLedgerPermissionsModeError, HttpResponse>>

Sends a request with this input using the given client.

Trait Implementations

impl Clone for UpdateLedgerPermissionsModeInputBuilder

fn clone(&self) -> UpdateLedgerPermissionsModeInputBuilder

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for UpdateLedgerPermissionsModeInputBuilder

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for UpdateLedgerPermissionsModeInputBuilder

fn default() -> UpdateLedgerPermissionsModeInputBuilder

Returns the “default value” for a type.

impl PartialEq for UpdateLedgerPermissionsModeInputBuilder

fn eq(&self, other: &UpdateLedgerPermissionsModeInputBuilder) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for UpdateLedgerPermissionsModeInputBuilder