Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG CICD is not deploying changes to the back-end #3898

Open
3 tasks done
OperationalFallacy opened this issue Jan 12, 2024 · 1 comment
Open
3 tasks done

BUG CICD is not deploying changes to the back-end #3898

OperationalFallacy opened this issue Jan 12, 2024 · 1 comment
Labels
feature-request New feature or request

Comments

@OperationalFallacy
Copy link

Before opening, please confirm:

Amplify Hosting feature

Backend builds

Is your feature request related to a problem? Please describe:

I've made some changes to the backend/function, added custom policy.

Local amplify shows the changes pending. Pushed it to the env branch, build runs - and... nothing

Local amplify still shows pending changes to the functions.

version: 1
applications:
  - appRoot: xxx-website
    backend:
      phases:
        install:
          commands:
            - pwd
            - cd ../xxx-api
            - node --version
            - nvm use 18
            - nvm use 18.17.0 || true
            - node --version
            - yarn global add tsc-alias typescript tsc
        build:
          commands:
            - yarn install --production
            - amplify --version
            - cat $(which amplifyPush) || true
            - amplifyPush --simple

Builds logs show changes to the resources

UPDATE_IN_PROGRESS                  functionXxx AWS::CloudFormation::Stack Fri Jan 12 2024 14:04:46 GMT+0000 (Coordinated Universal Time)

Build configured with Linux2023 image.

Describe how you'd like this feature to work

After the build, local amplify should not have any changes pending, right?!

@OperationalFallacy OperationalFallacy added the feature-request New feature or request label Jan 12, 2024
Copy link

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant