Amplify-console: on the CI/CD, amplifyPush should only deploy changes made (frontend/backend)

[aprilmintacpineda]

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug

• amplifyPush pushes backend even when there are no changes on the backend.
• amplifyPush pushes frontend even when there are no changes on the frontend.

Amplify CLI Version
4.24.1

To Reproduce

just use amplifyPush on the CI/CD

Expected behavior

• amplifyPush should skip the backend when there are no changes.
• amplifyPush should skip the frontend when there are no changes.

Screenshots

N/A

Desktop (please complete the following information):

• OS: N/A
• Node Version: N/A

Additional context

N/A

[UnleashedMind]

@aprilmintacpineda
Are you getting this on Amplify Console? If you we need to transfer this issue to the Console issue tracker.
The Amplify CLI does not push unless there is an update in your local development.

[aprilmintacpineda]

@UnleashedMind yes it's on the Continuous Deployment on the amplify console. I have the following amplify.yml

version: 1
backend:
  phases:
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --simple
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - yarn run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

[aprilmintacpineda]

Is it also updating other resources even when there are no changes? because it seems so..

[renebrandel]

Transferring this to console. cc @litwicki

[aprilmintacpineda]

Updated ticket description and title, please see above...

[RossWilliams]

I came to ask for a similar feature. My frontend build phase had a file corruption, but i couldn't quickly rebuild the frontend only, instead I needed to wait an extra 10 minutes for the backend to do nothing. I had this earlier when CloudFront decided to ignore my custom header changes and it took a long time to have the backend do nothing.

[keponk]

Have had same annoyance since the beginning of using Amplify. So far I ran with the assumption this is by design but now tracking this issue since I'd also appreciate being able to deploy only the frontend.

[hisham]

+1. Quick deployments are essential when doing emergency bug fixes. Backend does not need to be rebuilt if frontend only has changed. It just needs the aws-exports. Why is amplify push in my terminal smarter than amplify push via amplify console?

Smarter backend deployments will also save cost since AWS Amplify console charges per build minute.

[mansiva]

+1 Please AWS, this shouldn't be that hard to fix, CLI only updates what's changed, why can't the Console do the same??

[arturocanalda]

+1