|
5 | 5 | "AcknowledgeJob": "<p>Returns information about a specified job and whether that job has been received by the job worker. Only used for custom actions.</p>", |
6 | 6 | "AcknowledgeThirdPartyJob": "<p>Confirms a job worker has received the specified job. Only used for partner actions.</p>", |
7 | 7 | "CreateCustomActionType": "<p>Creates a new custom action that can be used in all pipelines associated with the AWS account. Only used for custom actions.</p>", |
8 | | - "CreatePipeline": "<p>Creates a pipeline.</p>", |
| 8 | + "CreatePipeline": "<p>Creates a pipeline.</p> <note> <p>In the pipeline structure, you must include either <code>artifactStore</code> or <code>artifactStores</code> in your pipeline, but you cannot use both. If you create a cross-region action in your pipeline, you must use <code>artifactStores</code>.</p> </note>", |
9 | 9 | "DeleteCustomActionType": "<p>Marks a custom action as deleted. <code>PollForJobs</code> for the custom action will fail after the action is marked for deletion. Only used for custom actions.</p> <important> <p>To re-create a custom action after it has been deleted you must use a string in the version field that has never been used before. This string can be an incremented version number, for example. To restore a deleted custom action, use a JSON file that is identical to the deleted action, including the original string in the version field.</p> </important>", |
10 | 10 | "DeletePipeline": "<p>Deletes the specified pipeline.</p>", |
11 | 11 | "DeleteWebhook": "<p>Deletes a previously created webhook by name. Deleting the webhook stops AWS CodePipeline from starting a pipeline every time an external event occurs. The API will return successfully when trying to delete a webhook that is already deleted. If a deleted webhook is re-created by calling PutWebhook with the same name, it will have a different URL.</p>", |
|
115 | 115 | "base": null, |
116 | 116 | "refs": { |
117 | 117 | "ActionConfiguration$configuration": "<p>The configuration data for the action.</p>", |
118 | | - "ActionDeclaration$configuration": "<p>The action declaration's configuration.</p>", |
| 118 | + "ActionDeclaration$configuration": "<p>The action's configuration. These are key-value pairs that specify input values for an action. For more information, see <a href=\"https://docs.aws.amazon.com/codepipeline/latest/userguide/reference-pipeline-structure.html#action-requirements\">Action Structure Requirements in CodePipeline</a>. For the list of configuration properties for the AWS CloudFormation action type in CodePipeline, see <a href=\"https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/continuous-delivery-codepipeline-action-reference.html\">Configuration Properties Reference</a> in the <i>AWS CloudFormation User Guide</i>. For template snippets with examples, see <a href=\"https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/continuous-delivery-codepipeline-parameter-override-functions.html\">Using Parameter Override Functions with CodePipeline Pipelines</a> in the <i>AWS CloudFormation User Guide</i>.</p> <p>The values can be represented in either JSON or YAML format. For example, the JSON configuration item format is as follows: </p> <p> <i>JSON:</i> </p> <p> <code>\"Configuration\" : { Key : Value },</code> </p>", |
119 | 119 | "ActionExecutionInput$configuration": "<p>Configuration data for an action execution.</p>" |
120 | 120 | } |
121 | 121 | }, |
|
292 | 292 | "ActionTypeId": { |
293 | 293 | "base": "<p>Represents information about an action type.</p>", |
294 | 294 | "refs": { |
295 | | - "ActionDeclaration$actionTypeId": "<p>The configuration information for the action type.</p>", |
| 295 | + "ActionDeclaration$actionTypeId": "<p>Specifies the action type and the provider of the action.</p>", |
296 | 296 | "ActionExecutionInput$actionTypeId": null, |
297 | 297 | "ActionType$id": "<p>Represents information about an action type.</p>", |
298 | 298 | "JobData$actionTypeId": "<p>Represents information about an action type.</p>", |
|
420 | 420 | } |
421 | 421 | }, |
422 | 422 | "ArtifactStore": { |
423 | | - "base": "<p>The Amazon S3 bucket where artifacts are stored for the pipeline.</p>", |
| 423 | + "base": "<p>The Amazon S3 bucket where artifacts are stored for the pipeline.</p> <note> <p>You must include either <code>artifactStore</code> or <code>artifactStores</code> in your pipeline, but you cannot use both. If you create a cross-region action in your pipeline, you must use <code>artifactStores</code>.</p> </note>", |
424 | 424 | "refs": { |
425 | 425 | "ArtifactStoreMap$value": null, |
426 | | - "PipelineDeclaration$artifactStore": "<p>Represents information about the Amazon S3 bucket where artifacts are stored for the pipeline. </p>" |
| 426 | + "PipelineDeclaration$artifactStore": "<p>Represents information about the Amazon S3 bucket where artifacts are stored for the pipeline.</p> <note> <p>You must include either <code>artifactStore</code> or <code>artifactStores</code> in your pipeline, but you cannot use both. If you create a cross-region action in your pipeline, you must use <code>artifactStores</code>.</p> </note>" |
427 | 427 | } |
428 | 428 | }, |
429 | 429 | "ArtifactStoreLocation": { |
|
435 | 435 | "ArtifactStoreMap": { |
436 | 436 | "base": null, |
437 | 437 | "refs": { |
438 | | - "PipelineDeclaration$artifactStores": "<p>A mapping of <code>artifactStore</code> objects and their corresponding regions. There must be an artifact store for the pipeline region and for each cross-region action within the pipeline. You can only use either <code>artifactStore</code> or <code>artifactStores</code>, not both.</p> <p>If you create a cross-region action in your pipeline, you must use <code>artifactStores</code>.</p>" |
| 438 | + "PipelineDeclaration$artifactStores": "<p>A mapping of <code>artifactStore</code> objects and their corresponding regions. There must be an artifact store for the pipeline region and for each cross-region action within the pipeline.</p> <note> <p>You must include either <code>artifactStore</code> or <code>artifactStores</code> in your pipeline, but you cannot use both. If you create a cross-region action in your pipeline, you must use <code>artifactStores</code>.</p> </note>" |
439 | 439 | } |
440 | 440 | }, |
441 | 441 | "ArtifactStoreType": { |
|
610 | 610 | "EncryptionKeyId": { |
611 | 611 | "base": null, |
612 | 612 | "refs": { |
613 | | - "EncryptionKey$id": "<p>The ID used to identify the key. For an AWS KMS key, this is the key ID or key ARN.</p>" |
| 613 | + "EncryptionKey$id": "<p>The ID used to identify the key. For an AWS KMS key, you can use the key ID, the key ARN, or the alias ARN.</p> <note> <p>Aliases are recognized only in the account that created the customer master key (CMK). For cross-account actions, you can only use the key ID or key ARN to identify the key.</p> </note>" |
614 | 614 | } |
615 | 615 | }, |
616 | 616 | "EncryptionKeyType": { |
|
647 | 647 | "ExecutionDetails$summary": "<p>The summary of the current status of the actions.</p>" |
648 | 648 | } |
649 | 649 | }, |
| 650 | + "ExecutionTrigger": { |
| 651 | + "base": "<p>The interaction or event that started a pipeline execution.</p>", |
| 652 | + "refs": { |
| 653 | + "PipelineExecutionSummary$trigger": "<p>The interaction or event that started a pipeline execution, such as automated change detection or a <code>StartPipelineExecution</code> API call.</p>" |
| 654 | + } |
| 655 | + }, |
650 | 656 | "ExternalExecutionId": { |
651 | 657 | "base": null, |
652 | 658 | "refs": { |
|
1603 | 1609 | "StageState$inboundTransitionState": "<p>The state of the inbound transition, which is either enabled or disabled.</p>" |
1604 | 1610 | } |
1605 | 1611 | }, |
| 1612 | + "TriggerDetail": { |
| 1613 | + "base": null, |
| 1614 | + "refs": { |
| 1615 | + "ExecutionTrigger$triggerDetail": "<p>Detail related to the event that started a pipeline execution, such as the webhook ARN of the webhook that triggered the pipeline execution or the user ARN for a user-initiated <code>start-pipeline-execution</code> CLI command.</p>" |
| 1616 | + } |
| 1617 | + }, |
| 1618 | + "TriggerType": { |
| 1619 | + "base": null, |
| 1620 | + "refs": { |
| 1621 | + "ExecutionTrigger$triggerType": "<p>The type of change-detection method, command, or user interaction that started a pipeline execution.</p>" |
| 1622 | + } |
| 1623 | + }, |
1606 | 1624 | "UntagResourceInput": { |
1607 | 1625 | "base": null, |
1608 | 1626 | "refs": { |
|
0 commit comments