aws / aws/aws-sam-cli

Request for More Info In Sam Deploy ChangeSet Failures

Open
#9,154 2 comments 0 reactions 0 assignees View on GitHub
stage/needs-triage type/feature
Dominant language
Python
Stars
6.7k
Forks
1.2k
Avg merge
1d 10h
Merged PRs (30d)
52

Description

### Describe your idea/feature/enhancement

I made changes to my template.yaml that caused my sam deploy to fail with this message: “Error: Failed to create changeset for the stack: fbp, ex: Waiter ChangeSetCreateComplete failed: Waiter encountered a terminal failure state: For expression "Status" we matched expected path: "FAILED" Status: FAILED. Reason: The following hook(s)/validation failed: [AWS::EarlyValidation::ResourceExistenceCheck]. To troubleshoot Early Validation errors, use the DescribeEvents API for detailed failure information.“

If I run this CLI:
aws cloudformation describe-events --stack-name --region us-east-1 --change-set-name "arn:aws:cloudformation:us-east-1:768286545465:changeSet/samcli-deploy1785624984/45c53ade-62a4-415f-ac7c-fc27e63b06d8”

I get output that shows me what the actual issue is.

### Proposal
Can the error ouput for sam deploy failures be augmented with more detailed error information? It would save developers a lot of time to be able to see this right away

Contributor guide

Open the contributing guide

Research direction

Start at the sam deploy changeset-failure handling and compare its current error output with the aws cloudformation describe-events command shown in the issue. Trace how the change-set name and stack name are available during deployment, then verify that the reported validation details appear directly in the failure message.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
cli, cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.