Build fail on unknown type from GraphQL Scheme

[bergmorten]

How did you install the Amplify CLI?

npm

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

20

Amplify CLI Version

12.10.2

What operating system are you using?

als2023 (amplify build console)

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

Nope

Describe the bug

Build that worked yesterday will not build today. Suspect it to be CLI version 12.10.2, works with 12.10.1.

In my GraphQL scheme I do have the following custome query:

enum BillingSource {
  CLIENT
  PROJECT
  FLEET
  DEPLOYMENT
}

input QuerySumBillingParamsInput {
  what: BillingSource!
  id: String # required for all except client
  billed: Boolean # null == all , false == unbilled true==billed
  from: AWSDateTime
  to: AWSDateTime
}

type Query {
  sumBilling(params: QuerySumBillingParamsInput!): Float
    @function(name: "billingFunction-${env}")
}

This has not been changed for a long time, and today amplify build fails with:

2024-03-07T10:35:46.418Z [WARNING]: ✖ There was an error initializing your environment.
2024-03-07T10:35:46.424Z [INFO]: 🛑 Unknown type QuerySumBillingParamsInput
                                 Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
2024-03-07T10:35:46.437Z [INFO]: 
2024-03-07T10:35:46.437Z [INFO]: Session Identifier: e0409621-5b2b-4afb-86bb-d38cf0535346
2024-03-07T10:35:46.547Z [ERROR]: !!! Build failed
2024-03-07T10:35:46.547Z [ERROR]: !!! Error: Command failed with exit code 1

Has support for custom input types been removed from queries?
If I downgrade to 12.10.1 it works...

Expected behavior

Should work as previous version 12.10.1

Reproduction steps

Try to build a grahql scheme with a query which has custom input variable

Project Identifier

0e0c35de10e80e85c555ebedce4575e5

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.

[espenbye]

Got the same issue here

[ykethan]

Hey folks, 👋 thanks for raising this! I'm going to transfer this over to our codegen repository for better assistance as this appears to be occurring on the model generation.

[sundersc]

We have identified a regression in CLI version 12.10.2 and rolled back latest to 12.10.1.

[github-actions]

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.