Adding Lambda function and pushing it displays override not implemented message

[ykethan]

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

How did you install the Amplify CLI?

No response

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

No response

Amplify CLI Version

8.4.0

What operating system are you using?

Windows

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

No

Amplify Categories

function

Amplify Commands

push

Describe the bug

With amplify CLI version 8.4.0 currently observing the following message on push. This is displayed when we add a lambda function and push it.

Overrides functionality is not implemented for this category

Note: this does not appear on amplify status. Possibly related to latest PR #9601

Expected behavior

The message is helpful but doesn't make sense if we have other categories as well. The documentation already provides this information.

Reproduction steps

1. amplify add function
2. select nodejs and no for all.
3. amplify push

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information

No response

[ngnathan]

I'm getting this error as well during the amplify console build process, and also even when I run amplify env checkout <env>.

But I didn't add or change much on the backend side, which was really confusing. But this error showed up on 8.4.0, but not on 8.3.1.

[ykethan]

hey @ngnathan, Thank you for reaching out. The message currently does not effect the application usage from my tests. The issue will be discussed as part of our weekly meetings.

[ykethan]

Note: The message appears to print a new statement for each Lambda function added.
Example: if 4 lambda function were added, 4 Overrides functionality is not implemented for this category messages are being displayed.

[hisham]

I noticed this message too when amplify is doing push. It's so vague, what category is it referring to? "Overrides functionality is not implemented for this category". I am just running 'amplify push', I have no idea what category it's referring to. I have to do the digging myself. Please make this error message more clear.

[vincent38wargnier]

I would say in general amplify cli messages are not so clear.

[ayasin]

I get this error and it's preventing my application from building the backend. The backend builds locally and deploys but times out on the server. This is true of new updates as well as builds that were previously working.

[StefanVolkmer-WW]

i also get this messages. The Number of Messages fits to the number of lambda functions.
But in my opinion this messages should not appear. And in general they are to vague. The Name of the Resource or at least the name of the category should be displayed.

i have 23 lambda functions.... a lot of messages.

[vincent38wargnier]

I currently gave up with v2 since we need specific configuration for lambda access through mutation pipes. Plus this message doesn't sound safe.

[alphonse92]

same here

[vincent38wargnier]

Any udpdates?