Skip to content
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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Jk/cumulus 3020 #3800

wants to merge 2 commits into from

Conversation

Jkovarik
Copy link
Member

Summary: Summary of changes

Addresses CUMULUS-3020

PR Checklist

  • Update CHANGELOG
  • Unit tests
  • Ad-hoc testing - Deploy changes and test manually
  • Integration tests

Copy link
Contributor

@npauzenga npauzenga left a 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"
Copy link
Contributor

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"
Copy link
Contributor

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
Copy link
Contributor

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
Copy link
Contributor

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.

Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants