httpApi timeout over 29 seconds message on functions that don't use the httpApi

Bug Report

Description

I have a function definition like this:

functions:

  website:
    handler: public/index.php
    timeout: 15 # seconds (max would be 29 though api gateway limitation)
    layers:
      - ${bref:layer.php-73-fpm}
    events:
      - httpApi: '*'

  console:
    handler: bin/console.php
    timeout: 120 # in seconds
    layers:
      - ${bref:layer.php-73}
      - ${bref:layer.console} # The "console" layer

This creates a warning

 Serverless Warning --------------------------------------
 
  Function timeout setting (120) is greater than maximum allowed timeout for HTTP API endpoint (29s). This may introduce situation where endpoint times out for succesful lambda invocation.

However, the function with 120 seconds timeout is not registered for the httpApi. This was introduced in #7420

[mhotchen]

@medikoo amazing; thanks for the fast response!

I work at a company that has helped over 10k people quit smoking. We rely heavily on serverless. I, and the whole company, really appreciate your work.

[medikoo]

@Nemo64 thanks for reporting, will be fixed with #7467

@mhotchen I’ve also ensured that function name is provided in eventual warning.

As you noted it’s an only a log pollution issue, it doesn’t affect functionality.