Running "amplify pull --yes" appears to cause upload/push.

Describe the bug Our build script performs an amplify pull --providers {filename} --frontend {filename} --amplify {filename} --yes. Recently we noticed that this is causing the environment to be pulled from the backend and then uploaded/pushed again. If we remove the --yes argument, then we are prompted with the question about making changes. We answer Y to this, and the pull happens as we expect (i.e. it is not followed up with an upload/push).

Amplify CLI Version We are running version 4.29.0 of the cli.

To Reproduce Perform a pull as mentioned int he description. Try it with and without the --yes switch to see the difference in behavior.

Expected behavior We expect that performing a pull will not cause any files to be uploaded or deployed to the environment on the backend.

Desktop (please complete the following information): Running on a Mac with 10.15.6. Node.js version is v10.21.0

[blydewright]

+1. We have a CD process setup through Vercel and require the --yes headless option, but since it runs a subsequent push after the pull, it slows down the deploy time significantly as we have a large app with many resources. The push is not expected or desired.

[github-actions[bot]]

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.