Skip to content

Use UUIDs for deploy ChangeSet names#10317

Open
rohan-patnaik wants to merge 1 commit into
aws:developfrom
rohan-patnaik:fix/cloudformation-changeset-uuid
Open

Use UUIDs for deploy ChangeSet names#10317
rohan-patnaik wants to merge 1 commit into
aws:developfrom
rohan-patnaik:fix/cloudformation-changeset-uuid

Conversation

@rohan-patnaik
Copy link
Copy Markdown

@rohan-patnaik rohan-patnaik commented May 16, 2026

Summary

Fixes #10315.

aws cloudformation deploy was generating ChangeSet names from a one-second timestamp. If two deploy commands started in the same second for the same stack, both could try to create the same ChangeSet name and one would fail with AlreadyExistsException.

This changes the generated ChangeSet name to use uuid.uuid4() while keeping the existing AWS CLI prefix. That keeps the name format valid and avoids collisions between concurrent deploys.

Testing

  • /tmp/awscli-10315-venv/bin/python -m pytest tests/unit/customizations/cloudformation/test_deployer.py
  • /tmp/awscli-10315-venv/bin/python -m py_compile awscli/customizations/cloudformation/deployer.py tests/unit/customizations/cloudformation/test_deployer.py

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cloudformation deploy: timestamp-only ChangeSet name guarantees collision under concurrent invocations

1 participant