#[non_exhaustive]pub struct PipelineDeclarationBuilder { /* private fields */ }
Expand description
A builder for PipelineDeclaration
.
Implementations§
Source§impl PipelineDeclarationBuilder
impl PipelineDeclarationBuilder
Sourcepub fn name(self, input: impl Into<String>) -> Self
pub fn name(self, input: impl Into<String>) -> Self
The name of the pipeline.
This field is required.Sourcepub fn role_arn(self, input: impl Into<String>) -> Self
pub fn role_arn(self, input: impl Into<String>) -> Self
The Amazon Resource Name (ARN) for CodePipeline to use to either perform actions with no actionRoleArn
, or to use to assume roles for actions with an actionRoleArn
.
Sourcepub fn set_role_arn(self, input: Option<String>) -> Self
pub fn set_role_arn(self, input: Option<String>) -> Self
The Amazon Resource Name (ARN) for CodePipeline to use to either perform actions with no actionRoleArn
, or to use to assume roles for actions with an actionRoleArn
.
Sourcepub fn get_role_arn(&self) -> &Option<String>
pub fn get_role_arn(&self) -> &Option<String>
The Amazon Resource Name (ARN) for CodePipeline to use to either perform actions with no actionRoleArn
, or to use to assume roles for actions with an actionRoleArn
.
Sourcepub fn artifact_store(self, input: ArtifactStore) -> Self
pub fn artifact_store(self, input: ArtifactStore) -> Self
Represents information about the S3 bucket where artifacts are stored for the pipeline.
You must include either artifactStore
or artifactStores
in your pipeline, but you cannot use both. If you create a cross-region action in your pipeline, you must use artifactStores
.
Sourcepub fn set_artifact_store(self, input: Option<ArtifactStore>) -> Self
pub fn set_artifact_store(self, input: Option<ArtifactStore>) -> Self
Represents information about the S3 bucket where artifacts are stored for the pipeline.
You must include either artifactStore
or artifactStores
in your pipeline, but you cannot use both. If you create a cross-region action in your pipeline, you must use artifactStores
.
Sourcepub fn get_artifact_store(&self) -> &Option<ArtifactStore>
pub fn get_artifact_store(&self) -> &Option<ArtifactStore>
Represents information about the S3 bucket where artifacts are stored for the pipeline.
You must include either artifactStore
or artifactStores
in your pipeline, but you cannot use both. If you create a cross-region action in your pipeline, you must use artifactStores
.
Sourcepub fn artifact_stores(self, k: impl Into<String>, v: ArtifactStore) -> Self
pub fn artifact_stores(self, k: impl Into<String>, v: ArtifactStore) -> Self
Adds a key-value pair to artifact_stores
.
To override the contents of this collection use set_artifact_stores
.
A mapping of artifactStore
objects and their corresponding Amazon Web Services Regions. There must be an artifact store for the pipeline Region and for each cross-region action in the pipeline.
You must include either artifactStore
or artifactStores
in your pipeline, but you cannot use both. If you create a cross-region action in your pipeline, you must use artifactStores
.
Sourcepub fn set_artifact_stores(
self,
input: Option<HashMap<String, ArtifactStore>>,
) -> Self
pub fn set_artifact_stores( self, input: Option<HashMap<String, ArtifactStore>>, ) -> Self
A mapping of artifactStore
objects and their corresponding Amazon Web Services Regions. There must be an artifact store for the pipeline Region and for each cross-region action in the pipeline.
You must include either artifactStore
or artifactStores
in your pipeline, but you cannot use both. If you create a cross-region action in your pipeline, you must use artifactStores
.
Sourcepub fn get_artifact_stores(&self) -> &Option<HashMap<String, ArtifactStore>>
pub fn get_artifact_stores(&self) -> &Option<HashMap<String, ArtifactStore>>
A mapping of artifactStore
objects and their corresponding Amazon Web Services Regions. There must be an artifact store for the pipeline Region and for each cross-region action in the pipeline.
You must include either artifactStore
or artifactStores
in your pipeline, but you cannot use both. If you create a cross-region action in your pipeline, you must use artifactStores
.
Sourcepub fn stages(self, input: StageDeclaration) -> Self
pub fn stages(self, input: StageDeclaration) -> Self
Appends an item to stages
.
To override the contents of this collection use set_stages
.
The stage in which to perform the action.
Sourcepub fn set_stages(self, input: Option<Vec<StageDeclaration>>) -> Self
pub fn set_stages(self, input: Option<Vec<StageDeclaration>>) -> Self
The stage in which to perform the action.
Sourcepub fn get_stages(&self) -> &Option<Vec<StageDeclaration>>
pub fn get_stages(&self) -> &Option<Vec<StageDeclaration>>
The stage in which to perform the action.
Sourcepub fn version(self, input: i32) -> Self
pub fn version(self, input: i32) -> Self
The version number of the pipeline. A new pipeline always has a version number of 1. This number is incremented when a pipeline is updated.
Sourcepub fn set_version(self, input: Option<i32>) -> Self
pub fn set_version(self, input: Option<i32>) -> Self
The version number of the pipeline. A new pipeline always has a version number of 1. This number is incremented when a pipeline is updated.
Sourcepub fn get_version(&self) -> &Option<i32>
pub fn get_version(&self) -> &Option<i32>
The version number of the pipeline. A new pipeline always has a version number of 1. This number is incremented when a pipeline is updated.
Sourcepub fn execution_mode(self, input: ExecutionMode) -> Self
pub fn execution_mode(self, input: ExecutionMode) -> Self
The method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
Sourcepub fn set_execution_mode(self, input: Option<ExecutionMode>) -> Self
pub fn set_execution_mode(self, input: Option<ExecutionMode>) -> Self
The method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
Sourcepub fn get_execution_mode(&self) -> &Option<ExecutionMode>
pub fn get_execution_mode(&self) -> &Option<ExecutionMode>
The method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
Sourcepub fn pipeline_type(self, input: PipelineType) -> Self
pub fn pipeline_type(self, input: PipelineType) -> Self
CodePipeline provides the following pipeline types, which differ in characteristics and price, so that you can tailor your pipeline features and cost to the needs of your applications.
-
V1 type pipelines have a JSON structure that contains standard pipeline, stage, and action-level parameters.
-
V2 type pipelines have the same structure as a V1 type, along with additional parameters for release safety and trigger configuration.
Including V2 parameters, such as triggers on Git tags, in the pipeline JSON when creating or updating a pipeline will result in the pipeline having the V2 type of pipeline and the associated costs.
For information about pricing for CodePipeline, see Pricing.
For information about which type of pipeline to choose, see What type of pipeline is right for me?.
Sourcepub fn set_pipeline_type(self, input: Option<PipelineType>) -> Self
pub fn set_pipeline_type(self, input: Option<PipelineType>) -> Self
CodePipeline provides the following pipeline types, which differ in characteristics and price, so that you can tailor your pipeline features and cost to the needs of your applications.
-
V1 type pipelines have a JSON structure that contains standard pipeline, stage, and action-level parameters.
-
V2 type pipelines have the same structure as a V1 type, along with additional parameters for release safety and trigger configuration.
Including V2 parameters, such as triggers on Git tags, in the pipeline JSON when creating or updating a pipeline will result in the pipeline having the V2 type of pipeline and the associated costs.
For information about pricing for CodePipeline, see Pricing.
For information about which type of pipeline to choose, see What type of pipeline is right for me?.
Sourcepub fn get_pipeline_type(&self) -> &Option<PipelineType>
pub fn get_pipeline_type(&self) -> &Option<PipelineType>
CodePipeline provides the following pipeline types, which differ in characteristics and price, so that you can tailor your pipeline features and cost to the needs of your applications.
-
V1 type pipelines have a JSON structure that contains standard pipeline, stage, and action-level parameters.
-
V2 type pipelines have the same structure as a V1 type, along with additional parameters for release safety and trigger configuration.
Including V2 parameters, such as triggers on Git tags, in the pipeline JSON when creating or updating a pipeline will result in the pipeline having the V2 type of pipeline and the associated costs.
For information about pricing for CodePipeline, see Pricing.
For information about which type of pipeline to choose, see What type of pipeline is right for me?.
Sourcepub fn variables(self, input: PipelineVariableDeclaration) -> Self
pub fn variables(self, input: PipelineVariableDeclaration) -> Self
Appends an item to variables
.
To override the contents of this collection use set_variables
.
A list that defines the pipeline variables for a pipeline resource. Variable names can have alphanumeric and underscore characters, and the values must match \[A-Za-z0-9@\-_\]+
.
Sourcepub fn set_variables(
self,
input: Option<Vec<PipelineVariableDeclaration>>,
) -> Self
pub fn set_variables( self, input: Option<Vec<PipelineVariableDeclaration>>, ) -> Self
A list that defines the pipeline variables for a pipeline resource. Variable names can have alphanumeric and underscore characters, and the values must match \[A-Za-z0-9@\-_\]+
.
Sourcepub fn get_variables(&self) -> &Option<Vec<PipelineVariableDeclaration>>
pub fn get_variables(&self) -> &Option<Vec<PipelineVariableDeclaration>>
A list that defines the pipeline variables for a pipeline resource. Variable names can have alphanumeric and underscore characters, and the values must match \[A-Za-z0-9@\-_\]+
.
Sourcepub fn triggers(self, input: PipelineTriggerDeclaration) -> Self
pub fn triggers(self, input: PipelineTriggerDeclaration) -> Self
Appends an item to triggers
.
To override the contents of this collection use set_triggers
.
The trigger configuration specifying a type of event, such as Git tags, that starts the pipeline.
When a trigger configuration is specified, default change detection for repository and branch commits is disabled.
Sourcepub fn set_triggers(
self,
input: Option<Vec<PipelineTriggerDeclaration>>,
) -> Self
pub fn set_triggers( self, input: Option<Vec<PipelineTriggerDeclaration>>, ) -> Self
The trigger configuration specifying a type of event, such as Git tags, that starts the pipeline.
When a trigger configuration is specified, default change detection for repository and branch commits is disabled.
Sourcepub fn get_triggers(&self) -> &Option<Vec<PipelineTriggerDeclaration>>
pub fn get_triggers(&self) -> &Option<Vec<PipelineTriggerDeclaration>>
The trigger configuration specifying a type of event, such as Git tags, that starts the pipeline.
When a trigger configuration is specified, default change detection for repository and branch commits is disabled.
Sourcepub fn build(self) -> Result<PipelineDeclaration, BuildError>
pub fn build(self) -> Result<PipelineDeclaration, BuildError>
Consumes the builder and constructs a PipelineDeclaration
.
This method will fail if any of the following fields are not set:
Trait Implementations§
Source§impl Clone for PipelineDeclarationBuilder
impl Clone for PipelineDeclarationBuilder
Source§fn clone(&self) -> PipelineDeclarationBuilder
fn clone(&self) -> PipelineDeclarationBuilder
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for PipelineDeclarationBuilder
impl Debug for PipelineDeclarationBuilder
Source§impl Default for PipelineDeclarationBuilder
impl Default for PipelineDeclarationBuilder
Source§fn default() -> PipelineDeclarationBuilder
fn default() -> PipelineDeclarationBuilder
impl StructuralPartialEq for PipelineDeclarationBuilder
Auto Trait Implementations§
impl Freeze for PipelineDeclarationBuilder
impl RefUnwindSafe for PipelineDeclarationBuilder
impl Send for PipelineDeclarationBuilder
impl Sync for PipelineDeclarationBuilder
impl Unpin for PipelineDeclarationBuilder
impl UnwindSafe for PipelineDeclarationBuilder
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>
Returns self
with the
fg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.bright_black());
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>
Returns self
with the
fg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.bright_green());
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.bright_yellow());
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>
Returns self
with the
fg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.bright_magenta());
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>
Returns self
with the
fg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.bright_white());
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>
Returns self
with the
bg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.on_bright_black());
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>
Returns self
with the
bg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.on_bright_green());
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.on_bright_yellow());
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightBlue
.
§Example
println!("{}", value.on_bright_blue());
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.on_bright_magenta());
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightCyan
.
§Example
println!("{}", value.on_bright_cyan());
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.on_bright_white());
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 underline(&self) -> Painted<&T>
fn underline(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::Underline
.
§Example
println!("{}", value.underline());
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::RapidBlink
.
§Example
println!("{}", value.rapid_blink());
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);