Cannot set multiple key-value for an alb event "query" with the same key

[Inqnuam]

Are you certain it's a bug?

• Yes, it looks like a bug

Is the issue caused by a plugin?

• It is not a plugin issue

Are you using the latest v3 release?

• Yes, I'm using the latest v3 release

Is there an existing issue for this?

• I have searched existing issues, it hasn't been reported yet

Issue description

AWS Application Load Balancer listener rule allows to set multiple values for a single query key.

Currently this is not possible with Serverless Framework as query "value" is defined as string.

Service configuration (serverless.yml) content

service: sls-project

frameworkVersion: "3"

package:
  individually: true

provider:
  name: aws
  runtime: nodejs18.x
  versionFunctions: false
  region: eu-west-3
  vpc:
    subnetIds: [subnet-0e2db7f9558f501d7, subnet-0cde9f3600cab039a]
    securityGroupIds: [sg-029d2fbba38db2dc7]

functions:
  lambda:
    handler: src/handlers/lambda.default
    events:
      - alb:
          listenerArn: arn:aws:elasticloadbalancing:xxxx
          priority: 936
          conditions:
            path: "/users"
            method: [GET]
            query:
              role: admin
              role: guest

Command name and used flags

"N/A

Command output

"N/A

Environment information

Framework Core: 3.29.0 (local)
Plugin: 6.2.3
SDK: 4.3.2

[medikoo]

@Inqnuam, thanks for opening. Indeed that's the case. It's a design bug on our side. Still it can be fixed. I propose following solution:

• Allow arrays for query property values
• Resolve arrays into multiple same query param values when resolving CF template

PR's welcome!

[Inqnuam]

Allo arrays for query property values
Resolve arrays into multiple same query param values when resolving CF template

This is what is did in my initial PR but figured out that with that schema we simply can't cover all possible conditions.
Please check the new isolated PR.

[medikoo]

@Inqnuam can you elaborate here, on other possible conditions that cannot be covered with what I propsoed (let's discuss this fully here, until we agree on best solution)