From 2905d176eadbc9af7f367eef6adc060da887d612 Mon Sep 17 00:00:00 2001
From: awstools You can retry a stage that has failed without having to run a pipeline again from the beginning. You do
- * this by either retrying the failed actions in a stage or by retrying all actions in the stage starting from the first action in the stage. When you retry the failed actions in a stage,
- * all actions that are still in progress continue working, and failed actions are
- * triggered again. When you retry a failed stage from the first action in the stage, the stage cannot have any actions in progress. Before a stage can be retried, it must either have all actions failed or some actions failed and some succeeded. You can retry a stage that has failed without having to run a pipeline again from
+ * the beginning. You do this by either retrying the failed actions in a stage or by
+ * retrying all actions in the stage starting from the first action in the stage. When you
+ * retry the failed actions in a stage, all actions that are still in progress continue
+ * working, and failed actions are triggered again. When you retry a failed stage from the
+ * first action in the stage, the stage cannot have any actions in progress. Before a stage
+ * can be retried, it must either have all actions failed or some actions failed and some
+ * succeeded.
A timeout duration in minutes that can be applied against the ActionType’s default + * timeout value specified in Quotas for CodePipeline + * . This attribute is available only to the manual approval ActionType.
+ */ + timeoutInMinutes?: number; } /** @@ -835,7 +843,8 @@ export type StartTimeRange = (typeof StartTimeRange)[keyof typeof StartTimeRange /** * @public - *The field that specifies to filter on the latest execution in the pipeline.
+ *The field that specifies to filter on the latest execution in the + * pipeline.
*Filtering on the latest execution is available for executions run on or after * February 08, 2024.
@@ -2002,18 +2011,21 @@ export interface StageDeclaration { /** * @public - *The Git repository branches specified as filter criteria to start the pipeline.
+ *The Git repository branches specified as filter criteria to start the + * pipeline.
*/ export interface GitBranchFilterCriteria { /** * @public - *The list of patterns of Git branches that, when a commit is pushed, are to be included as criteria that starts the pipeline.
+ *The list of patterns of Git branches that, when a commit is pushed, are to be + * included as criteria that starts the pipeline.
*/ includes?: string[]; /** * @public - *The list of patterns of Git branches that, when a commit is pushed, are to be excluded from starting the pipeline.
+ *The list of patterns of Git branches that, when a commit is pushed, are to be + * excluded from starting the pipeline.
*/ excludes?: string[]; } @@ -2035,42 +2047,49 @@ export type GitPullRequestEventType = (typeof GitPullRequestEventType)[keyof typ /** * @public - *The Git repository file paths specified as filter criteria to start the pipeline.
+ *The Git repository file paths specified as filter criteria to start the + * pipeline.
*/ export interface GitFilePathFilterCriteria { /** * @public - *The list of patterns of Git repository file paths that, when a commit is pushed, are to be included as criteria that starts the pipeline.
+ *The list of patterns of Git repository file paths that, when a commit is pushed, + * are to be included as criteria that starts the pipeline.
*/ includes?: string[]; /** * @public - *The list of patterns of Git repository file paths that, when a commit is pushed, are to be excluded from starting the pipeline.
+ *The list of patterns of Git repository file paths that, when a commit is pushed, + * are to be excluded from starting the pipeline.
*/ excludes?: string[]; } /** * @public - *The event criteria for the pull request trigger configuration, such as the lists of branches or file paths to include and exclude.
+ *The event criteria for the pull request trigger configuration, such as the lists of + * branches or file paths to include and exclude.
*/ export interface GitPullRequestFilter { /** * @public - *The field that specifies which pull request events to filter on (opened, updated, closed) for the trigger configuration.
+ *The field that specifies which pull request events to filter on (opened, updated, + * closed) for the trigger configuration.
*/ events?: GitPullRequestEventType[]; /** * @public - *The field that specifies to filter on branches for the pull request trigger configuration.
+ *The field that specifies to filter on branches for the pull request trigger + * configuration.
*/ branches?: GitBranchFilterCriteria; /** * @public - *The field that specifies to filter on file paths for the pull request trigger configuration.
+ *The field that specifies to filter on file paths for the pull request trigger + * configuration.
*/ filePaths?: GitFilePathFilterCriteria; } @@ -2098,7 +2117,9 @@ export interface GitTagFilterCriteria { /** * @public - *The event criteria that specify when a specified repository event will start the pipeline for the specified trigger configuration, such as the lists of Git tags to include and exclude.
+ *The event criteria that specify when a specified repository event will start the + * pipeline for the specified trigger configuration, such as the lists of Git tags to + * include and exclude.
*/ export interface GitPushFilter { /** @@ -2110,13 +2131,15 @@ export interface GitPushFilter { /** * @public - *The field that specifies to filter on branches for the push trigger configuration.
+ *The field that specifies to filter on branches for the push trigger + * configuration.
*/ branches?: GitBranchFilterCriteria; /** * @public - *The field that specifies to filter on file paths for the push trigger configuration.
+ *The field that specifies to filter on file paths for the push trigger + * configuration.
*/ filePaths?: GitFilePathFilterCriteria; } @@ -2151,7 +2174,8 @@ export interface GitConfiguration { /** * @public - *The field where the repository event that will start the pipeline is specified as pull requests.
+ *The field where the repository event that will start the pipeline is specified as + * pull requests.
*/ pullRequest?: GitPullRequestFilter[]; } @@ -2218,7 +2242,8 @@ export interface PipelineVariableDeclaration { /** * @public - *The description of a pipeline-level variable. It's used to add additional context about the variable, and not being used at time when pipeline executes.
+ *The description of a pipeline-level variable. It's used to add additional context + * about the variable, and not being used at time when pipeline executes.
*/ description?: string; } @@ -2284,15 +2309,16 @@ export interface PipelineDeclaration { /** * @public - *The method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
+ *The method that the pipeline will use to handle multiple executions. The default + * mode is SUPERSEDED.
*/ executionMode?: ExecutionMode; /** * @public - *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.
+ *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, @@ -2309,8 +2335,8 @@ export interface PipelineDeclaration { * 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?.
+ *For information about which type of pipeline to choose, see What type of + * pipeline is right for me?.
*/ pipelineType?: PipelineType; @@ -2324,7 +2350,8 @@ export interface PipelineDeclaration { /** * @public - *The trigger configuration specifying a type of event, such as Git tags, that starts the pipeline.
+ *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.
@@ -3208,7 +3235,8 @@ export interface PipelineExecution { /** * @public - *The method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
+ *The method that the pipeline will use to handle multiple executions. The default + * mode is SUPERSEDED.
*/ executionMode?: ExecutionMode; } @@ -3841,7 +3869,8 @@ export interface PipelineExecutionSummary { /** * @public - *The method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
+ *The method that the pipeline will use to handle multiple executions. The default + * mode is SUPERSEDED.
*/ executionMode?: ExecutionMode; } @@ -3906,9 +3935,9 @@ export interface PipelineSummary { /** * @public - *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.
+ *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, @@ -3925,14 +3954,15 @@ export interface PipelineSummary { * 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?.
+ *For information about which type of pipeline to choose, see What type of + * pipeline is right for me?.
*/ pipelineType?: PipelineType; /** * @public - *The method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
+ *The method that the pipeline will use to handle multiple executions. The default + * mode is SUPERSEDED.
*/ executionMode?: ExecutionMode; @@ -5100,8 +5130,9 @@ export interface StartPipelineExecutionInput { /** * @public - *A list that overrides pipeline variables for a pipeline execution that's being started. Variable names must match [A-Za-z0-9@\-_]+
,
- * and the values can be anything except an empty string.
A list that overrides pipeline variables for a pipeline execution that's being
+ * started. Variable names must match [A-Za-z0-9@\-_]+
, and the values can be
+ * anything except an empty string.
A list that allows you to specify, or override, the source revision for a pipeline execution that's being started. A source revision is the version with all the changes to your application code, or source artifact, for the pipeline execution.
+ *A list that allows you to specify, or override, the source revision for a pipeline + * execution that's being started. A source revision is the version with all the changes to + * your application code, or source artifact, for the pipeline execution.
*/ sourceRevisions?: SourceRevisionOverride[]; } diff --git a/codegen/sdk-codegen/aws-models/codepipeline.json b/codegen/sdk-codegen/aws-models/codepipeline.json index f6a91146cda5..acb236e96ec3 100644 --- a/codegen/sdk-codegen/aws-models/codepipeline.json +++ b/codegen/sdk-codegen/aws-models/codepipeline.json @@ -475,6 +475,12 @@ "traits": { "smithy.api#documentation": "The variable namespace associated with the action. All variables produced as output by\n this action fall under this namespace.
" } + }, + "timeoutInMinutes": { + "target": "com.amazonaws.codepipeline#ActionTimeout", + "traits": { + "smithy.api#documentation": "A timeout duration in minutes that can be applied against the ActionType’s default\n timeout value specified in Quotas for CodePipeline\n . This attribute is available only to the manual approval ActionType.
" + } } }, "traits": { @@ -936,6 +942,15 @@ "target": "com.amazonaws.codepipeline#ActionState" } }, + "com.amazonaws.codepipeline#ActionTimeout": { + "type": "integer", + "traits": { + "smithy.api#range": { + "min": 5, + "max": 86400 + } + } + }, "com.amazonaws.codepipeline#ActionType": { "type": "structure", "members": { @@ -4074,18 +4089,18 @@ "includes": { "target": "com.amazonaws.codepipeline#GitBranchPatternList", "traits": { - "smithy.api#documentation": "The list of patterns of Git branches that, when a commit is pushed, are to be included as criteria that starts the pipeline.
" + "smithy.api#documentation": "The list of patterns of Git branches that, when a commit is pushed, are to be\n included as criteria that starts the pipeline.
" } }, "excludes": { "target": "com.amazonaws.codepipeline#GitBranchPatternList", "traits": { - "smithy.api#documentation": "The list of patterns of Git branches that, when a commit is pushed, are to be excluded from starting the pipeline.
" + "smithy.api#documentation": "The list of patterns of Git branches that, when a commit is pushed, are to be\n excluded from starting the pipeline.
" } } }, "traits": { - "smithy.api#documentation": "The Git repository branches specified as filter criteria to start the pipeline.
" + "smithy.api#documentation": "The Git repository branches specified as filter criteria to start the\n pipeline.
" } }, "com.amazonaws.codepipeline#GitBranchNamePattern": { @@ -4129,7 +4144,7 @@ "pullRequest": { "target": "com.amazonaws.codepipeline#GitPullRequestFilterList", "traits": { - "smithy.api#documentation": "The field where the repository event that will start the pipeline is specified as pull requests.
" + "smithy.api#documentation": "The field where the repository event that will start the pipeline is specified as\n pull requests.
" } } }, @@ -4143,18 +4158,18 @@ "includes": { "target": "com.amazonaws.codepipeline#GitFilePathPatternList", "traits": { - "smithy.api#documentation": "The list of patterns of Git repository file paths that, when a commit is pushed, are to be included as criteria that starts the pipeline.
" + "smithy.api#documentation": "The list of patterns of Git repository file paths that, when a commit is pushed,\n are to be included as criteria that starts the pipeline.
" } }, "excludes": { "target": "com.amazonaws.codepipeline#GitFilePathPatternList", "traits": { - "smithy.api#documentation": "The list of patterns of Git repository file paths that, when a commit is pushed, are to be excluded from starting the pipeline.
" + "smithy.api#documentation": "The list of patterns of Git repository file paths that, when a commit is pushed,\n are to be excluded from starting the pipeline.
" } } }, "traits": { - "smithy.api#documentation": "The Git repository file paths specified as filter criteria to start the pipeline.
" + "smithy.api#documentation": "The Git repository file paths specified as filter criteria to start the\n pipeline.
" } }, "com.amazonaws.codepipeline#GitFilePathPattern": { @@ -4220,24 +4235,24 @@ "events": { "target": "com.amazonaws.codepipeline#GitPullRequestEventTypeList", "traits": { - "smithy.api#documentation": "The field that specifies which pull request events to filter on (opened, updated, closed) for the trigger configuration.
" + "smithy.api#documentation": "The field that specifies which pull request events to filter on (opened, updated,\n closed) for the trigger configuration.
" } }, "branches": { "target": "com.amazonaws.codepipeline#GitBranchFilterCriteria", "traits": { - "smithy.api#documentation": "The field that specifies to filter on branches for the pull request trigger configuration.
" + "smithy.api#documentation": "The field that specifies to filter on branches for the pull request trigger\n configuration.
" } }, "filePaths": { "target": "com.amazonaws.codepipeline#GitFilePathFilterCriteria", "traits": { - "smithy.api#documentation": "The field that specifies to filter on file paths for the pull request trigger configuration.
" + "smithy.api#documentation": "The field that specifies to filter on file paths for the pull request trigger\n configuration.
" } } }, "traits": { - "smithy.api#documentation": "The event criteria for the pull request trigger configuration, such as the lists of branches or file paths to include and exclude.
" + "smithy.api#documentation": "The event criteria for the pull request trigger configuration, such as the lists of\n branches or file paths to include and exclude.
" } }, "com.amazonaws.codepipeline#GitPullRequestFilterList": { @@ -4264,18 +4279,18 @@ "branches": { "target": "com.amazonaws.codepipeline#GitBranchFilterCriteria", "traits": { - "smithy.api#documentation": "The field that specifies to filter on branches for the push trigger configuration.
" + "smithy.api#documentation": "The field that specifies to filter on branches for the push trigger\n configuration.
" } }, "filePaths": { "target": "com.amazonaws.codepipeline#GitFilePathFilterCriteria", "traits": { - "smithy.api#documentation": "The field that specifies to filter on file paths for the push trigger configuration.
" + "smithy.api#documentation": "The field that specifies to filter on file paths for the push trigger\n configuration.
" } } }, "traits": { - "smithy.api#documentation": "The event criteria that specify when a specified repository event will start the pipeline for the specified trigger configuration, such as the lists of Git tags to include and exclude.
" + "smithy.api#documentation": "The event criteria that specify when a specified repository event will start the\n pipeline for the specified trigger configuration, such as the lists of Git tags to\n include and exclude.
" } }, "com.amazonaws.codepipeline#GitPushFilterList": { @@ -4835,7 +4850,7 @@ } }, "traits": { - "smithy.api#documentation": "The field that specifies to filter on the latest execution in the pipeline.
\nFiltering on the latest execution is available for executions run on or after\n February 08, 2024.
\nThe field that specifies to filter on the latest execution in the\n pipeline.
\nFiltering on the latest execution is available for executions run on or after\n February 08, 2024.
\nThe method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
" + "smithy.api#documentation": "The method that the pipeline will use to handle multiple executions. The default\n mode is SUPERSEDED.
" } }, "pipelineType": { "target": "com.amazonaws.codepipeline#PipelineType", "traits": { - "smithy.api#documentation": "CodePipeline provides the following pipeline types, which differ in characteristics and\n price, so that you can tailor your pipeline features and cost to the needs of your\n applications.
\nV1 type pipelines have a JSON structure that contains standard pipeline,\n stage, and action-level parameters.
\nV2 type pipelines have the same structure as a V1 type, along with additional\n parameters for release safety and trigger configuration.
\nIncluding V2 parameters, such as triggers on Git tags, in the pipeline JSON when\n creating or updating a pipeline will result in the pipeline having the V2 type of\n pipeline and the associated costs.
\nFor information about pricing for CodePipeline, see Pricing.
\n\n For information about which type of pipeline to choose, see What type of pipeline is right for me?.
" + "smithy.api#documentation": "CodePipeline provides the following pipeline types, which differ in\n characteristics and price, so that you can tailor your pipeline features and cost to the\n needs of your applications.
\nV1 type pipelines have a JSON structure that contains standard pipeline,\n stage, and action-level parameters.
\nV2 type pipelines have the same structure as a V1 type, along with additional\n parameters for release safety and trigger configuration.
\nIncluding V2 parameters, such as triggers on Git tags, in the pipeline JSON when\n creating or updating a pipeline will result in the pipeline having the V2 type of\n pipeline and the associated costs.
\nFor information about pricing for CodePipeline, see Pricing.
\nFor information about which type of pipeline to choose, see What type of\n pipeline is right for me?.
" } }, "variables": { @@ -5639,7 +5654,7 @@ "triggers": { "target": "com.amazonaws.codepipeline#PipelineTriggerDeclarationList", "traits": { - "smithy.api#documentation": "The trigger configuration specifying a type of event, such as Git tags, that starts the pipeline.
\nWhen a trigger configuration is specified, default change detection for\n repository and branch commits is disabled.
\nThe trigger configuration specifying a type of event, such as Git tags, that starts\n the pipeline.
\nWhen a trigger configuration is specified, default change detection for\n repository and branch commits is disabled.
\nThe method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
" + "smithy.api#documentation": "The method that the pipeline will use to handle multiple executions. The default\n mode is SUPERSEDED.
" } } }, @@ -5837,7 +5852,7 @@ "executionMode": { "target": "com.amazonaws.codepipeline#ExecutionMode", "traits": { - "smithy.api#documentation": "The method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
" + "smithy.api#documentation": "The method that the pipeline will use to handle multiple executions. The default\n mode is SUPERSEDED.
" } } }, @@ -5953,13 +5968,13 @@ "pipelineType": { "target": "com.amazonaws.codepipeline#PipelineType", "traits": { - "smithy.api#documentation": "CodePipeline provides the following pipeline types, which differ in characteristics and\n price, so that you can tailor your pipeline features and cost to the needs of your\n applications.
\nV1 type pipelines have a JSON structure that contains standard pipeline,\n stage, and action-level parameters.
\nV2 type pipelines have the same structure as a V1 type, along with additional\n parameters for release safety and trigger configuration.
\nIncluding V2 parameters, such as triggers on Git tags, in the pipeline JSON when\n creating or updating a pipeline will result in the pipeline having the V2 type of\n pipeline and the associated costs.
\nFor information about pricing for CodePipeline, see Pricing.
\n\n For information about which type of pipeline to choose, see What type of pipeline is right for me?.
" + "smithy.api#documentation": "CodePipeline provides the following pipeline types, which differ in\n characteristics and price, so that you can tailor your pipeline features and cost to the\n needs of your applications.
\nV1 type pipelines have a JSON structure that contains standard pipeline,\n stage, and action-level parameters.
\nV2 type pipelines have the same structure as a V1 type, along with additional\n parameters for release safety and trigger configuration.
\nIncluding V2 parameters, such as triggers on Git tags, in the pipeline JSON when\n creating or updating a pipeline will result in the pipeline having the V2 type of\n pipeline and the associated costs.
\nFor information about pricing for CodePipeline, see Pricing.
\nFor information about which type of pipeline to choose, see What type of\n pipeline is right for me?.
" } }, "executionMode": { "target": "com.amazonaws.codepipeline#ExecutionMode", "traits": { - "smithy.api#documentation": "The method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.
" + "smithy.api#documentation": "The method that the pipeline will use to handle multiple executions. The default\n mode is SUPERSEDED.
" } }, "created": { @@ -6082,7 +6097,7 @@ "description": { "target": "com.amazonaws.codepipeline#PipelineVariableDescription", "traits": { - "smithy.api#documentation": "The description of a pipeline-level variable. It's used to add additional context about the variable, and not being used at time when pipeline executes.
" + "smithy.api#documentation": "The description of a pipeline-level variable. It's used to add additional context\n about the variable, and not being used at time when pipeline executes.
" } } }, @@ -6966,7 +6981,7 @@ } ], "traits": { - "smithy.api#documentation": "You can retry a stage that has failed without having to run a pipeline again from the beginning. You do\n this by either retrying the failed actions in a stage or by retrying all actions in the stage starting from the first action in the stage. When you retry the failed actions in a stage,\n all actions that are still in progress continue working, and failed actions are\n triggered again. When you retry a failed stage from the first action in the stage, the stage cannot have any actions in progress. Before a stage can be retried, it must either have all actions failed or some actions failed and some succeeded.
" + "smithy.api#documentation": "You can retry a stage that has failed without having to run a pipeline again from\n the beginning. You do this by either retrying the failed actions in a stage or by\n retrying all actions in the stage starting from the first action in the stage. When you\n retry the failed actions in a stage, all actions that are still in progress continue\n working, and failed actions are triggered again. When you retry a failed stage from the\n first action in the stage, the stage cannot have any actions in progress. Before a stage\n can be retried, it must either have all actions failed or some actions failed and some\n succeeded.
" } }, "com.amazonaws.codepipeline#RetryStageExecutionInput": { @@ -7531,7 +7546,7 @@ "variables": { "target": "com.amazonaws.codepipeline#PipelineVariableList", "traits": { - "smithy.api#documentation": "A list that overrides pipeline variables for a pipeline execution that's being started. Variable names must match [A-Za-z0-9@\\-_]+
, \n and the values can be anything except an empty string.
A list that overrides pipeline variables for a pipeline execution that's being\n started. Variable names must match [A-Za-z0-9@\\-_]+
, and the values can be\n anything except an empty string.
A list that allows you to specify, or override, the source revision for a pipeline execution that's being started. A source revision is the version with all the changes to your application code, or source artifact, for the pipeline execution.
" + "smithy.api#documentation": "A list that allows you to specify, or override, the source revision for a pipeline\n execution that's being started. A source revision is the version with all the changes to\n your application code, or source artifact, for the pipeline execution.
" } } },