#[non_exhaustive]pub struct UpdateAppInput {Show 22 fields
pub app_id: Option<String>,
pub name: Option<String>,
pub description: Option<String>,
pub platform: Option<Platform>,
pub compute_role_arn: Option<String>,
pub iam_service_role_arn: Option<String>,
pub environment_variables: Option<HashMap<String, String>>,
pub enable_branch_auto_build: Option<bool>,
pub enable_branch_auto_deletion: Option<bool>,
pub enable_basic_auth: Option<bool>,
pub basic_auth_credentials: Option<String>,
pub custom_rules: Option<Vec<CustomRule>>,
pub build_spec: Option<String>,
pub custom_headers: Option<String>,
pub enable_auto_branch_creation: Option<bool>,
pub auto_branch_creation_patterns: Option<Vec<String>>,
pub auto_branch_creation_config: Option<AutoBranchCreationConfig>,
pub repository: Option<String>,
pub oauth_token: Option<String>,
pub access_token: Option<String>,
pub job_config: Option<JobConfig>,
pub cache_config: Option<CacheConfig>,
}
Expand description
The request structure for the update app request.
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.app_id: Option<String>
The unique ID for an Amplify app.
name: Option<String>
The name for an Amplify app.
description: Option<String>
The description for an Amplify app.
platform: Option<Platform>
The platform for the Amplify app. For a static app, set the platform type to WEB
. For a dynamic server-side rendered (SSR) app, set the platform type to WEB_COMPUTE
. For an app requiring Amplify Hosting's original SSR support only, set the platform type to WEB_DYNAMIC
.
If you are deploying an SSG only app with Next.js version 14 or later, you must set the platform type to WEB_COMPUTE
.
compute_role_arn: Option<String>
The Amazon Resource Name (ARN) of the IAM role to assign to an SSR app. The SSR Compute role allows the Amplify Hosting compute service to securely access specific Amazon Web Services resources based on the role's permissions. For more information about the SSR Compute role, see Adding an SSR Compute role in the Amplify User Guide.
iam_service_role_arn: Option<String>
The Amazon Resource Name (ARN) of the IAM service role for the Amplify app.
environment_variables: Option<HashMap<String, String>>
The environment variables for an Amplify app.
enable_branch_auto_build: Option<bool>
Enables branch auto-building for an Amplify app.
enable_branch_auto_deletion: Option<bool>
Automatically disconnects a branch in the Amplify console when you delete a branch from your Git repository.
enable_basic_auth: Option<bool>
Enables basic authorization for an Amplify app.
basic_auth_credentials: Option<String>
The basic authorization credentials for an Amplify app. You must base64-encode the authorization credentials and provide them in the format user:password
.
custom_rules: Option<Vec<CustomRule>>
The custom redirect and rewrite rules for an Amplify app.
build_spec: Option<String>
The build specification (build spec) for an Amplify app.
custom_headers: Option<String>
The custom HTTP headers for an Amplify app.
enable_auto_branch_creation: Option<bool>
Enables automated branch creation for an Amplify app.
auto_branch_creation_patterns: Option<Vec<String>>
Describes the automated branch creation glob patterns for an Amplify app.
auto_branch_creation_config: Option<AutoBranchCreationConfig>
The automated branch creation configuration for an Amplify app.
repository: Option<String>
The name of the Git repository for an Amplify app.
oauth_token: Option<String>
The OAuth token for a third-party source control system for an Amplify app. The OAuth token is used to create a webhook and a read-only deploy key using SSH cloning. The OAuth token is not stored.
Use oauthToken
for repository providers other than GitHub, such as Bitbucket or CodeCommit.
To authorize access to GitHub as your repository provider, use accessToken
.
You must specify either oauthToken
or accessToken
when you update an app.
Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
access_token: Option<String>
The personal access token for a GitHub repository for an Amplify app. The personal access token is used to authorize access to a GitHub repository using the Amplify GitHub App. The token is not stored.
Use accessToken
for GitHub repositories only. To authorize access to a repository provider such as Bitbucket or CodeCommit, use oauthToken
.
You must specify either accessToken
or oauthToken
when you update an app.
Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
job_config: Option<JobConfig>
Describes the configuration details that apply to the jobs for an Amplify app.
cache_config: Option<CacheConfig>
The cache configuration for the Amplify app.
Implementations§
Source§impl UpdateAppInput
impl UpdateAppInput
Sourcepub fn description(&self) -> Option<&str>
pub fn description(&self) -> Option<&str>
The description for an Amplify app.
Sourcepub fn platform(&self) -> Option<&Platform>
pub fn platform(&self) -> Option<&Platform>
The platform for the Amplify app. For a static app, set the platform type to WEB
. For a dynamic server-side rendered (SSR) app, set the platform type to WEB_COMPUTE
. For an app requiring Amplify Hosting's original SSR support only, set the platform type to WEB_DYNAMIC
.
If you are deploying an SSG only app with Next.js version 14 or later, you must set the platform type to WEB_COMPUTE
.
Sourcepub fn compute_role_arn(&self) -> Option<&str>
pub fn compute_role_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the IAM role to assign to an SSR app. The SSR Compute role allows the Amplify Hosting compute service to securely access specific Amazon Web Services resources based on the role's permissions. For more information about the SSR Compute role, see Adding an SSR Compute role in the Amplify User Guide.
Sourcepub fn iam_service_role_arn(&self) -> Option<&str>
pub fn iam_service_role_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the IAM service role for the Amplify app.
Sourcepub fn environment_variables(&self) -> Option<&HashMap<String, String>>
pub fn environment_variables(&self) -> Option<&HashMap<String, String>>
The environment variables for an Amplify app.
Sourcepub fn enable_branch_auto_build(&self) -> Option<bool>
pub fn enable_branch_auto_build(&self) -> Option<bool>
Enables branch auto-building for an Amplify app.
Sourcepub fn enable_branch_auto_deletion(&self) -> Option<bool>
pub fn enable_branch_auto_deletion(&self) -> Option<bool>
Automatically disconnects a branch in the Amplify console when you delete a branch from your Git repository.
Sourcepub fn enable_basic_auth(&self) -> Option<bool>
pub fn enable_basic_auth(&self) -> Option<bool>
Enables basic authorization for an Amplify app.
Sourcepub fn basic_auth_credentials(&self) -> Option<&str>
pub fn basic_auth_credentials(&self) -> Option<&str>
The basic authorization credentials for an Amplify app. You must base64-encode the authorization credentials and provide them in the format user:password
.
Sourcepub fn custom_rules(&self) -> &[CustomRule]
pub fn custom_rules(&self) -> &[CustomRule]
The custom redirect and rewrite rules for an Amplify app.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .custom_rules.is_none()
.
Sourcepub fn build_spec(&self) -> Option<&str>
pub fn build_spec(&self) -> Option<&str>
The build specification (build spec) for an Amplify app.
Sourcepub fn custom_headers(&self) -> Option<&str>
pub fn custom_headers(&self) -> Option<&str>
The custom HTTP headers for an Amplify app.
Sourcepub fn enable_auto_branch_creation(&self) -> Option<bool>
pub fn enable_auto_branch_creation(&self) -> Option<bool>
Enables automated branch creation for an Amplify app.
Sourcepub fn auto_branch_creation_patterns(&self) -> &[String]
pub fn auto_branch_creation_patterns(&self) -> &[String]
Describes the automated branch creation glob patterns for an Amplify app.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .auto_branch_creation_patterns.is_none()
.
Sourcepub fn auto_branch_creation_config(&self) -> Option<&AutoBranchCreationConfig>
pub fn auto_branch_creation_config(&self) -> Option<&AutoBranchCreationConfig>
The automated branch creation configuration for an Amplify app.
Sourcepub fn repository(&self) -> Option<&str>
pub fn repository(&self) -> Option<&str>
The name of the Git repository for an Amplify app.
Sourcepub fn oauth_token(&self) -> Option<&str>
pub fn oauth_token(&self) -> Option<&str>
The OAuth token for a third-party source control system for an Amplify app. The OAuth token is used to create a webhook and a read-only deploy key using SSH cloning. The OAuth token is not stored.
Use oauthToken
for repository providers other than GitHub, such as Bitbucket or CodeCommit.
To authorize access to GitHub as your repository provider, use accessToken
.
You must specify either oauthToken
or accessToken
when you update an app.
Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
Sourcepub fn access_token(&self) -> Option<&str>
pub fn access_token(&self) -> Option<&str>
The personal access token for a GitHub repository for an Amplify app. The personal access token is used to authorize access to a GitHub repository using the Amplify GitHub App. The token is not stored.
Use accessToken
for GitHub repositories only. To authorize access to a repository provider such as Bitbucket or CodeCommit, use oauthToken
.
You must specify either accessToken
or oauthToken
when you update an app.
Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
Sourcepub fn job_config(&self) -> Option<&JobConfig>
pub fn job_config(&self) -> Option<&JobConfig>
Describes the configuration details that apply to the jobs for an Amplify app.
Sourcepub fn cache_config(&self) -> Option<&CacheConfig>
pub fn cache_config(&self) -> Option<&CacheConfig>
The cache configuration for the Amplify app.
Source§impl UpdateAppInput
impl UpdateAppInput
Sourcepub fn builder() -> UpdateAppInputBuilder
pub fn builder() -> UpdateAppInputBuilder
Creates a new builder-style object to manufacture UpdateAppInput
.
Trait Implementations§
Source§impl Clone for UpdateAppInput
impl Clone for UpdateAppInput
Source§fn clone(&self) -> UpdateAppInput
fn clone(&self) -> UpdateAppInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for UpdateAppInput
impl Debug for UpdateAppInput
Source§impl PartialEq for UpdateAppInput
impl PartialEq for UpdateAppInput
impl StructuralPartialEq for UpdateAppInput
Auto Trait Implementations§
impl Freeze for UpdateAppInput
impl RefUnwindSafe for UpdateAppInput
impl Send for UpdateAppInput
impl Sync for UpdateAppInput
impl Unpin for UpdateAppInput
impl UnwindSafe for UpdateAppInput
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);