From 0b5c17c75bdb55a2565a64430046f51f4fefc60b Mon Sep 17 00:00:00 2001 From: Adam Ruka Date: Tue, 25 Sep 2018 10:40:31 -0700 Subject: [PATCH] feat(aws-cloudformation): update the ReadMe of the module to reflect the new Action names. Follow up from #771. --- packages/@aws-cdk/aws-cloudformation/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/packages/@aws-cdk/aws-cloudformation/README.md b/packages/@aws-cdk/aws-cloudformation/README.md index 044f9ecab0780..8ea59a126634c 100644 --- a/packages/@aws-cdk/aws-cloudformation/README.md +++ b/packages/@aws-cdk/aws-cloudformation/README.md @@ -18,14 +18,14 @@ for more details about using CloudFormation in CodePipeline. This package defines the following actions: -* **CreateUpdateStack** - Deploy a CloudFormation template directly from the pipeline. The indicated stack is created, +* **PipelineCreateUpdateStackAction** - Deploy a CloudFormation template directly from the pipeline. The indicated stack is created, or updated if it already exists. If the stack is in a failure state, deployment will fail (unless `replaceOnFailure` is set to `true`, in which case it will be destroyed and recreated). -* **DeleteStackOnly** - Delete the stack with the given name. -* **CreateReplaceChangeSet** - Prepare a change set to be applied later. You will typically use change sets if you want +* **PipelineDeleteStackAction** - Delete the stack with the given name. +* **PipelineCreateReplaceChangeSetAction** - Prepare a change set to be applied later. You will typically use change sets if you want to manually verify the changes that are being staged, or if you want to separate the people (or system) preparing the changes from the people (or system) applying the changes. -* **ExecuteChangeSet** - Execute a change set prepared previously. +* **PipelineExecuteChangeSetAction** - Execute a change set prepared previously. ### Custom Resources