-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Lambda Function URL HTTP request and response types #436
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
// Copyright 2022 Amazon.com, Inc. or its affiliates. All Rights Reserved. | ||
|
||
package events | ||
|
||
// LambdaFunctionURLRequest contains data coming from the HTTP request to a Lambda Function URL. | ||
type LambdaFunctionURLRequest struct { | ||
Version string `json:"version"` // Version is expected to be `"2.0"` | ||
RawPath string `json:"rawPath"` | ||
RawQueryString string `json:"rawQueryString"` | ||
Cookies []string `json:"cookies,omitempty"` | ||
Headers map[string]string `json:"headers"` | ||
QueryStringParameters map[string]string `json:"queryStringParameters,omitempty"` | ||
RequestContext LambdaFunctionURLRequestContext `json:"requestContext"` | ||
Body string `json:"body,omitempty"` | ||
IsBase64Encoded bool `json:"isBase64Encoded"` | ||
} | ||
|
||
// LambdaFunctionURLRequestContext contains the information to identify the AWS account and resources invoking the Lambda function. | ||
type LambdaFunctionURLRequestContext struct { | ||
AccountID string `json:"accountId"` | ||
RequestID string `json:"requestId"` | ||
Authorizer *LambdaFunctionURLRequestContextAuthorizerDescription `json:"authorizer,omitempty"` | ||
APIID string `json:"apiId"` // APIID is the Lambda URL ID | ||
DomainName string `json:"domainName"` // DomainName is of the format `"<url-id>.lambda-url.<region>.on.aws"` | ||
DomainPrefix string `json:"domainPrefix"` // DomainPrefix is the Lambda URL ID | ||
Time string `json:"time"` | ||
TimeEpoch int64 `json:"timeEpoch"` | ||
HTTP LambdaFunctionURLRequestContextHTTPDescription `json:"http"` | ||
} | ||
|
||
// LambdaFunctionURLRequestContextAuthorizerDescription contains authorizer information for the request context. | ||
type LambdaFunctionURLRequestContextAuthorizerDescription struct { | ||
IAM *LambdaFunctionURLRequestContextAuthorizerIAMDescription `json:"iam,omitempty"` | ||
} | ||
|
||
// LambdaFunctionURLRequestContextAuthorizerIAMDescription contains IAM information for the request context. | ||
type LambdaFunctionURLRequestContextAuthorizerIAMDescription struct { | ||
AccessKey string `json:"accessKey"` | ||
AccountID string `json:"accountId"` | ||
CallerID string `json:"callerId"` | ||
UserARN string `json:"userArn"` | ||
UserID string `json:"userId"` | ||
} | ||
|
||
// LambdaFunctionURLRequestContextHTTPDescription contains HTTP information for the request context. | ||
type LambdaFunctionURLRequestContextHTTPDescription struct { | ||
Method string `json:"method"` | ||
Path string `json:"path"` | ||
Protocol string `json:"protocol"` | ||
SourceIP string `json:"sourceIp"` | ||
UserAgent string `json:"userAgent"` | ||
} | ||
|
||
// LambdaFunctionURLResponse configures the HTTP response to be returned by Lambda Function URL for the request. | ||
type LambdaFunctionURLResponse struct { | ||
StatusCode int `json:"statusCode"` | ||
Headers map[string]string `json:"headers"` | ||
Body string `json:"body"` | ||
IsBase64Encoded bool `json:"isBase64Encoded"` | ||
Cookies []string `json:"cookies"` | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
// Copyright 2022 Amazon.com, Inc. or its affiliates. All Rights Reserved. | ||
|
||
package events | ||
|
||
import ( | ||
"encoding/json" | ||
"io/ioutil" | ||
"testing" | ||
|
||
"github.com/stretchr/testify/assert" | ||
) | ||
|
||
func TestLambdaFunctionURLResponseMarshaling(t *testing.T) { | ||
|
||
// read json from file | ||
inputJSON, err := ioutil.ReadFile("./testdata/lambda-urls-response.json") | ||
if err != nil { | ||
t.Errorf("could not open test file. details: %v", err) | ||
} | ||
|
||
// de-serialize into Go object | ||
var inputEvent LambdaFunctionURLResponse | ||
if err := json.Unmarshal(inputJSON, &inputEvent); err != nil { | ||
t.Errorf("could not unmarshal event. details: %v", err) | ||
} | ||
|
||
// serialize to json | ||
outputJSON, err := json.Marshal(inputEvent) | ||
if err != nil { | ||
t.Errorf("could not marshal event. details: %v", err) | ||
} | ||
|
||
assert.JSONEq(t, string(inputJSON), string(outputJSON)) | ||
} | ||
|
||
func TestLambdaFunctionURLRequestMarshaling(t *testing.T) { | ||
|
||
// read json from file | ||
inputJSON, err := ioutil.ReadFile("./testdata/lambda-urls-request.json") | ||
if err != nil { | ||
t.Errorf("could not open test file. details: %v", err) | ||
} | ||
|
||
// de-serialize into Go object | ||
var inputEvent LambdaFunctionURLRequest | ||
if err := json.Unmarshal(inputJSON, &inputEvent); err != nil { | ||
t.Errorf("could not unmarshal event. details: %v", err) | ||
} | ||
|
||
// serialize to json | ||
outputJSON, err := json.Marshal(inputEvent) | ||
if err != nil { | ||
t.Errorf("could not marshal event. details: %v", err) | ||
} | ||
|
||
assert.JSONEq(t, string(inputJSON), string(outputJSON)) | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
{ | ||
"version": "2.0", | ||
"rawPath": "/my/path", | ||
"rawQueryString": "parameter1=value1¶meter1=value2¶meter2=value", | ||
"cookies": [ | ||
"cookie1", | ||
"cookie2" | ||
], | ||
"headers": { | ||
"header1": "value1", | ||
"header2": "value1,value2" | ||
}, | ||
"queryStringParameters": { | ||
"parameter1": "value1,value2", | ||
"parameter2": "value" | ||
}, | ||
"requestContext": { | ||
"accountId": "123456789012", | ||
"apiId": "<urlid>", | ||
"authorizer": { | ||
"iam": { | ||
"accessKey": "AKIA...", | ||
"accountId": "111122223333", | ||
"callerId": "AIDA...", | ||
"userArn": "arn:aws:iam::111122223333:user/example-user", | ||
"userId": "AIDA..." | ||
} | ||
}, | ||
"domainName": "<url-id>.lambda-url.us-west-2.on.aws", | ||
"domainPrefix": "<url-id>", | ||
"http": { | ||
"method": "POST", | ||
"path": "/my/path", | ||
"protocol": "HTTP/1.1", | ||
"sourceIp": "123.123.123.123", | ||
"userAgent": "agent" | ||
}, | ||
"requestId": "id", | ||
"time": "12/Mar/2020:19:03:58 +0000", | ||
"timeEpoch": 1583348638390 | ||
}, | ||
"body": "Hello from client!", | ||
"isBase64Encoded": false | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
{ | ||
"statusCode": 201, | ||
"headers": { | ||
"Content-Type": "application/json", | ||
"My-Custom-Header": "Custom Value" | ||
}, | ||
"body": "{ \"message\": \"Hello, world!\" }", | ||
"cookies": [ | ||
"Cookie_1=Value1; Expires=21 Oct 2021 07:48 GMT", | ||
"Cookie_2=Value2; Max-Age=78000" | ||
], | ||
"isBase64Encoded": false | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably be
map[string][]string
or similar to events.APIGatewayProxyRequest. (Same comment forLambdaFunctionURLResponse
)Bringing this up mainly because both HTTP header and URL query strings can have multiple keys of the same value.
Header:
query:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lambda Function URLs ended up copying the API Gateway payload 2.0 shape, which I believe got rid of the MultiValue*** option - events.APIGatewayV2HTTPRequest
I'll double check what the Lambda Function URLs behavior is when a client sends multi value headers/query, maybe there is the option for a custom MarshalJSON/UnmarshalJSON so that the struct consumer can still get a
map[string][]string
- is that what you had in mind @jasdel ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
verified that the function urls respects multi-value query string and multi-value headers, but concatenates with
,
rather than representing as an array in the jsonmy echo function:
my test case:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I came up with this approach to make the
.Headers
field more easily assignable to the stdlibhttp.Headers
type. The same could be done forurl.Values
for the.QueryStringParameters
fieldWhich was neat, but I'm not 100% convinced this is the right approach for this struct. I'd hoped instead to be able to legally cast like
var values map[string]commaSeperatedValue; headers := http.Header(values)
, but go's type system seemed to demand themake(...)
and re-assignment loop, which felt marginally wasteful.I poked @carlzogh again about this, and right now I'm leaning to keep this PR as-is rather than extending the serialization.
.Header
or.QueryStringParameters
fields.longer term, I'm open to smarter serialization for the http proxy event sources, as either some
v2
types with a richer set of built-in types and appropriate documentation for construction, or with a higher abstraction layer that hides the json goo behind the stdlibhttp.Request/http.ResponseWriter
typesThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Current implementation that joins multiple headers makes sense, given the API gateway 2.0 style. I'd suggestion not added automatic splitting on commas though, because comma being a delimiter in a header is dependent on the header, and requires domain knowledge.
For example a common date format,
HTTP-Date
,Wed, 21 Oct 2015 07:28:00 GMT
. Contains a comma in its value. Logic that splits on commas without domain knowledge of the header would produce the wrong result. Leaving header value splitting to the consumer probably is the best path forward.