Changes Not Detected in AWS Stack During UPDATE_IN_PROGRESS State

[azadvt]

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v18.17.0

Amplify CLI Version

12.13.0

What operating system are you using?

Windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Our team is experiencing an issue where changes push to amplify it is not being detected during the UPDATE_IN_PROGRESS state. Despite making modifications to the stack, the deployment process fails to recognize these changes and does not update the environment as expected.

Screen.Recording.2024-10-28.111854.mp4

Describe the bug

Make changes to the AWS stack configuration (e.g., in a CloudFormation template).
Deploy the stack and initiate an update.
Observe that the stack enters the UPDATE_IN_PROGRESS state but does not apply or recognize the recent changes.

Expected behavior

Expected Behavior: The AWS stack should detect and apply all recent changes during the update process.

Reproduction steps

Run amplify pull to pull the latest environment setup in an empty directory.
Make any changes to the Amplify backend (e.g., modify a parameter in a resource configuration file).
Run amplify push to deploy the changes.

Project Identifier

report-1730106208042.zip

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[ykethan]

Hey @azadvt, thank you for reaching out. Could you provide us some additional information on the changes made on the resources(ex: lambda, api) during the deployment?

[ykethan]

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.