-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: Deployment options. Use pre-built package by default. #40
Conversation
2fcff34
to
6156c71
Compare
# Include main requirements | ||
-r ../costnotifier/requirements.txt | ||
|
||
# Additional packages to install when doing testing |
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.
One nice thing with this change.
Only install boto3 when doing tests. It is already available within the lambda environment :D
@@ -36,16 +57,21 @@ module "billing_notifier_lambda" { | |||
function_name = var.naming_prefix | |||
description = var.lambda_description | |||
|
|||
handler = "handler.report_cost" | |||
handler = "app.lambda_handler" | |||
runtime = var.runtime | |||
timeout = 300 | |||
|
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.
Removing this means we no longer depend on the remote build environment
a988d73
to
df0356f
Compare
I'll also do some testing in TF in our internal environments to check the lambda is still working :) |
df0356f
to
c61a4f3
Compare
c61a4f3
to
1ad57a3
Compare
Tagged with 0.42.0 for testing and rolled to our root account |
Tests passed, merging. |
No description provided.