使用AWS Chalice开发Lambda时兼容原有嵌套查询参数的方案

Absolutely, you can pull this off without making your existing clients change a single line of code—here are two reliable approaches that work seamlessly with AWS Chalice and API Gateway:

Solution 1: Use API Gateway Mapping Templates to Rewrite Query Params #

API Gateway doesn't natively parse key[] style params into arrays, but you can use mapping templates to transform the raw request data before it reaches your Lambda function. Here's how:

1. After deploying your Chalice app, head to the API Gateway console and locate your API's /save GET method.
2. Navigate to the Integration Request section, then expand Mapping Templates.
3. Add a new template for application/json (or match the content type your clients send).
4. Paste this VTL (Velocity Template Language) code to parse multi-value query params into arrays:

{
  "queryStringParameters": {
    #foreach($param in $input.params().querystring.keySet())
      "$param": [
        #foreach($value in $input.params().querystring.get($param))
          "$value"#if($foreach.hasNext),#end
        #end
      ]#if($foreach.hasNext),#end
    #end
  }
}

5. Save the template and redeploy your API stage.

In your Chalice function, you can access the parsed array like this:

from chalice import Chalice

app = Chalice(app_name='your-app')

@app.route('/save', methods=['GET'])
def save():
    # Access the array from the transformed query params
    logstrings = app.current_request.query_params.getlist('logstring[]')
    return {'status': 'success', 'logstrings': logstrings}

Solution 2: Parse the Raw Query String Directly in Chalice (Recommended) #

If you prefer to avoid modifying API Gateway configurations, you can parse the raw query string directly in your Chalice code using Python's built-in urllib.parse module. This is simpler and keeps all logic within your Lambda function.

Here's the code:

from chalice import Chalice
import urllib.parse

app = Chalice(app_name='your-app')

@app.route('/save', methods=['GET'])
def save():
    # Get the raw, unmodified query string from the request
    raw_query = app.current_request.raw_query_string
    # Parse it into a dictionary where multi-value params become lists
    parsed_params = urllib.parse.parse_qs(raw_query, keep_blank_values=True)
    
    # Extract the logstring[] values (will be a list even if only one value is sent)
    logstrings = parsed_params.get('logstring[]', [])
    
    # Your business logic here
    return {'status': 'success', 'received_logstrings': logstrings}

Why this works: #

The parse_qs function automatically detects when a parameter is repeated (like logstring[]=usrid&logstring[]=passed) and returns a list of values for that key. Even if a client sends a single logstring[]=foo, you'll get ['foo']—consistent with how nested params are handled in traditional web frameworks.

Both approaches let you keep the exact request structure your clients already use, so no changes are needed on their end. The second method is my go-to because it's self-contained and doesn't require manual API Gateway setup.

内容的提问来源于stack exchange，提问作者Vedank Kulshrestha