-
Notifications
You must be signed in to change notification settings - Fork 394
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
test mr #97
base: main
Are you sure you want to change the base?
test mr #97
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,3 +24,7 @@ functions: | |
- httpApi: | ||
path: /api/github/webhooks | ||
method: post | ||
memorySize: | ||
- 256 | ||
timeout: 30 | ||
logRetentionInDays: 14 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This code patch adds two new configuration options to a function:
There don't appear to be any bug risks with this code patch. However, it would be helpful to confirm that the existing configuration options set elsewhere in the file are appropriate for this function. Additionally, it may be worth considering whether the timeout value of 30 seconds is sufficient for this function's expected runtime. |
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 code patch seems to be adding a configuration to a serverless function.
The added
memorySize
value sets the maximum amount of memory that can be allocated to the function, which could affect its performance depending on the workload.The
timeout
value sets the maximum execution time of the function, after which it will be terminated.The
logRetentionInDays
value sets how long the logs generated by the function should be retained.These changes seem reasonable and there are no obvious bugs. However, without knowledge of the context or the rest of the codebase, it's difficult to say if these changes will be sufficient or optimal for your use case.