renaming model causes build failure which causes Data manager to fail

[ykethan]

Before opening, please confirm:

• 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.
• I have removed any sensitive information from my code snippets and submission.

App Id

du64f5tz2v3sc

Region

us-east-1

Environment name

dev

Figma File Version (if applicable)

No response

Amplify CLI Version

No response

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

No response

What operating system are you using?

No response

Browser type?

No response

Describe the bug

When renaming a model say from Events to Event and deploy the model. The deployment fails with error

Only one resolver is allowed per field.

When going back to Data manager and creating a record causes the record to stay in a never ending sync status

workaround: remove data model, deploy and re-add the data model and deploy. not ideal for production envs.

Expected behavior

dont cause the data manager fails if deployment rolls back

Reproduction steps

1. Create a Model Events as follows

enum EnumCountry {
  INDIA
  AUSTRALIA
  CANADA
  USA
  UK
}

type Events @model @auth(rules: [{allow: public}]) {
  id: ID!
  country: EnumCountry!
  city: String!
  venue: String!
  address1: String!
  addess2: String
  time: String!
  startDate: String!
  endDate: String!
  phone: String
}

2. rename model from Events to Event
3. see deployment fail
4. go to data manager
5. create a record and observe a never ending sync issue

Project Identifier

No response

Additional information

No response

[ykethan]

Closing the issue, the API deploy should throw error when renaming the data model.
An error occurred while processing your request: Cannot use model name "Event" due to conflict with the existing API resource.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

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.
If you wish to keep having a conversation with other community members under this issue feel free to do so.