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

amplify push doesn't deploy for container based rest apis #2228

Closed
2 tasks done
zandvakiliramin opened this issue Jan 29, 2024 · 4 comments
Closed
2 tasks done

amplify push doesn't deploy for container based rest apis #2228

zandvakiliramin opened this issue Jan 29, 2024 · 4 comments
Labels
api-rest containers pending-community-response Issue is pending a response from the author or community. pending-response transferred

Comments

@zandvakiliramin
Copy link

How did you install the Amplify CLI?

npm

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

v20.8.0

Amplify CLI Version

12.7.0

What operating system are you using?

Mac

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

No manual changes made

Describe the bug

I created a rest API using a Docker container a few months ago. When I try to update it now, using amplify push, I get Deployment state saved successfully in the end, but no change is made to the ecs. I checked the link for the code pipeline, and above the page it is written:

As of 2 months agoChange 2 months ago to UTC-6:00 time formatChange 2 months ago to UTC-6:00 time format, CodePipeline has disabled polling in this pipeline because it hasn't run in the 30 days prior. Use the recommended event-based mechanism to start new pipeline executions.

Also, when I checked the pipeline, it was from 3 months ago, and it does not get updated.

Expected behavior

I expect the changes to be deployed.

Reproduction steps

  1. Make an amplify rest api using a docker container
  2. Don't update it for three months
  3. Try updating it and redeploying it

Project Identifier

64645b8840605258eb3b7de823f2c831

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
Copy link
Member

ykethan commented Jan 29, 2024

Hey,👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂.

@ykethan ykethan transferred this issue from aws-amplify/amplify-cli Jan 29, 2024
@AnilMaktala
Copy link
Member

Hey @zandvakiliramin, thanks for raising this issue and providing the repro steps.

We will reproduce this internally and report back soon.

@AnilMaktala AnilMaktala added pending-response pending-community-response Issue is pending a response from the author or community. labels Oct 28, 2024
@AnilMaktala
Copy link
Member

Hi @zandvakiliramin, We were unable to reproduce the issue by following the steps mentioned in the description. We recommend trying the latest CLI version. If you still encounter the same problem after upgrading, please feel free to leave a comment. This will allow us to reopen the issue and provide you with the necessary support.

@AnilMaktala AnilMaktala closed this as not planned Won't fix, can't repro, duplicate, stale Nov 11, 2024
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-rest containers pending-community-response Issue is pending a response from the author or community. pending-response transferred
Projects
None yet
Development

No branches or pull requests

4 participants