Struct aws_sdk_codepipeline::types::PipelineSummary

#[non_exhaustive]
pub struct PipelineSummary {
    pub name: Option<String>,
    pub version: Option<i32>,
    pub pipeline_type: Option<PipelineType>,
    pub created: Option<DateTime>,
    pub updated: Option<DateTime>,
}

Returns a summary of a pipeline.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

name: Option<String>

The name of the pipeline.

version: Option<i32>

The version number of the pipeline.

pipeline_type: 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?.

V2 type pipelines, along with triggers on Git tags and pipeline-level variables, are not currently supported for CloudFormation and CDK resources in CodePipeline. For more information about V2 type pipelines, see Pipeline types in the CodePipeline User Guide.

created: Option<DateTime>

The date and time the pipeline was created, in timestamp format.

updated: Option<DateTime>

The date and time of the last update to the pipeline, in timestamp format.

Implementations

impl PipelineSummary

pub fn name(&self) -> Option<&str>

The name of the pipeline.

pub fn version(&self) -> Option<i32>

The version number of the pipeline.

pub fn 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?.

V2 type pipelines, along with triggers on Git tags and pipeline-level variables, are not currently supported for CloudFormation and CDK resources in CodePipeline. For more information about V2 type pipelines, see Pipeline types in the CodePipeline User Guide.

pub fn created(&self) -> Option<&DateTime>

The date and time the pipeline was created, in timestamp format.

pub fn updated(&self) -> Option<&DateTime>

The date and time of the last update to the pipeline, in timestamp format.

impl PipelineSummary

pub fn builder() -> PipelineSummaryBuilder

Creates a new builder-style object to manufacture PipelineSummary.

Trait Implementations

impl Clone for PipelineSummary

fn clone(&self) -> PipelineSummary

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Debug for PipelineSummary

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

Formats the value using the given formatter.

impl PartialEq for PipelineSummary

fn eq(&self, other: &PipelineSummary) -> 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 PipelineSummary