aws / aws/aws-cli

Add --change-set-name to aws cloudformation deploy command

Open
#5,435 3 comments 25 reactions 0 assignees View on GitHub
cloudformation package-deploy customization feature-request p3
Dominant language
Python
Stars
17.3k
Forks
4.6k
Avg merge
1d 2h
Merged PRs (30d)
13

Description

**Is your feature request related to a problem? Please describe.**

I would like to have CI/CD process which looks like this:

1. Create a new change set for review:

```
aws cloudformation deploy \
--stack-name XXX \
--change-set-name ${BRANCH_NAME}-${BUILD_ID} \
--no-execute-changeset \
...
```

2. Display what will be changed:

```
aws cloudformation describe-change-set \
--stack-name XXX \
--change-set-name ${BRANCH_NAME}-${BUILD_ID} \
...
```

3. Wait for confirmation
4. Execute change set

```
aws cloudformation change-set-execute \
--stack-name XXX \
--change-set-name ${BRANCH_NAME}-${BUILD_ID} \
...
```

**Describe the solution you'd like**

I would like to add a new parameter `--change-set-name` to the `deploy` command, so CI/CD service can set its own name for the new change set.

**Describe alternatives you've considered**

1. Use `aws cloudformation create-change-set`

It doesn't solve problems that `deploy` command solves, for example I don't need to think about `--change-set-type` (`CREATE` or `UPDATE`).

2. Query (filter) the output of `aws cloudformation deploy --no-execute-changeset`

A change set name `awscli-cloudformation-package-deploy-*` is not descriptive and I would like to have better names in logs and CloudFormation UI :)

I can try to impelement this new feature as my first pull request, but first I would like to know what do you think :)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.