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

v6.3.0 breaks container deployment #8412

Closed
4 tasks done
mattfysh opened this issue Oct 10, 2021 · 2 comments · Fixed by #8416
Closed
4 tasks done

v6.3.0 breaks container deployment #8412

mattfysh opened this issue Oct 10, 2021 · 2 comments · Fixed by #8416
Labels
bug Something isn't working containers Issues related to the non-serverless container based functionality

Comments

@mattfysh
Copy link

Before opening, please confirm:

  • I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
  • I have searched for duplicate or closed issues.
  • I have read the guide for submitting bug reports.
  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?

pnpm

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

v16.10.0

Amplify CLI Version

6.3.0

What operating system are you using?

Mac

Amplify Categories

api

Amplify Commands

push

Describe the bug

When trying to deploy containers with v6.3.0 I receive this message:

CREATE_FAILED               apiRepository                                         AWS::ECR::Repository       Sun Oct 10 2021 01:13:49 GMT+0000 (Coordinated Universal Time) Resource handler returned message: "Resource of type 'AWS::ECR::Repository' with identifier '<snip>' already exists." 

I received this message twice, then downgraded to v6.2.1 and was able to deploy successfully

Expected behavior

The deploy goes as expected

Reproduction steps

  1. Deploy a serverless container
  2. Make a change
  3. Deploy it again - see error about AWS::ECR::Repository already existing

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line


Additional information

No response

@ammarkarachi ammarkarachi added bug Something isn't working containers Issues related to the non-serverless container based functionality labels Oct 10, 2021
@ammarkarachi
Copy link
Contributor

@mattfysh I could reproduce will have a fix out soon. Thanks for the issue.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working containers Issues related to the non-serverless container based functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants