-
Notifications
You must be signed in to change notification settings - Fork 106
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
Jk/cumulus 3020 #3800
base: master
Are you sure you want to change the base?
Jk/cumulus 3020 #3800
Conversation
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.
Looks good @Jkovarik, just one nit about the description to make it painfully obvious what the unit is.
variable "sf_event_sqs_lambda_timeout" { | ||
type = number | ||
default = null | ||
description = "A timeout override for the sf_event_sqs_to_db_records lambda. Defaults to (var.rds_connection_timing_configuration.acquireTimeoutMillis / 1000) + 60). Use with caution, system instability may result if modified" |
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.
Could we specify that the unit is milliseconds? Assuming that's correct 😄
variable "sf_event_sqs_lambda_timeout" { | ||
type = number | ||
default = null | ||
description = "A timeout override for the sf_event_sqs_to_db_records lambda. Defaults to (var.rds_connection_timing_configuration.acquireTimeoutMillis / 1000) + 60). Use with caution, system instability may result if modified" |
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.
Same comment as above.
# between the IAM role, queue and lambda function. | ||
sf_event_sqs_lambda_timeout = (var.rds_connection_timing_configuration.acquireTimeoutMillis / 1000) + 60 | ||
# between the IAM role, queue, and lambda function. | ||
sf_event_sqs_lambda_timeout = var.sf_event_sqs_lambda_timeout != null ? var.sf_event_sqs_lambda_timeout : (var.rds_connection_timing_configuration.acquireTimeoutMillis / 1000) + 60 |
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 paused on the explicit comparison to null but that's the default so seems fine. I don't see how this would be undefined.
@@ -23,6 +23,7 @@ module "archive" { | |||
elasticsearch_security_group_id = var.elasticsearch_security_group_id | |||
elasticsearch_remove_index_alias_conflict = var.elasticsearch_remove_index_alias_conflict | |||
|
|||
sf_event_sqs_lambda_timeout = var.sf_event_sqs_lambda_timeout |
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.
Should we update the example terraform? I always ask this and the answer is usually "it's not intended to exemplify all possible options". I think it's fine not to, just raising it for kicks.
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.
The main benefit as I see it would just be documentation if users are looking at the example config. It's probably best to have it well documented in the variables tf like you have it.
Summary: Summary of changes
Addresses CUMULUS-3020
PR Checklist