-
Notifications
You must be signed in to change notification settings - Fork 21
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: more lambda config options #573
feat: more lambda config options #573
Conversation
@@ -4,6 +4,16 @@ variable "aws_region" { | |||
default = "us-east-1" | |||
} | |||
|
|||
variable "aws_access_key" { |
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.
Let's use named profiles (with profile
) instead of aws_access_key
and aws_secret_access_key
. Static creds are increasingly 💀 .
https://registry.terraform.io/providers/hashicorp/aws/latest/docs#profile
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.
Fixed it 👌
Looks good - one small fix re: |
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.
🚢
* v0.18.0 * feat: extend cors (#578) * fix: cors not applied to all routes (#577) * feat: improve schema read (#576) * feat: collect ip fingerprint and better tstamp (#575) * feat: log schema metadata (#574) * feat: more lambda config options (#573) * fet: more lambda config options * chore: remove unused var * review --------- Co-authored-by: Léonard Henriquez <leonard@topo.io>
Added new features to make the Lambda terraform config more versatile: