-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
Add log_delivery_configuration
#168
Conversation
/test all |
/test all |
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.
Change details
-
Error ID Change Path Resource BC_AWS_GENERAL_9 Added /main.tf aws_elasticache_replication_group.default BC_AWS_GENERAL_111 Added /main.tf aws_elasticache_replication_group.default BC_AWS_GENERAL_10 Added /main.tf aws_elasticache_replication_group.default
/test all |
/test all |
/test all |
@@ -144,6 +143,17 @@ resource "aws_elasticache_replication_group" "default" { | |||
final_snapshot_identifier = var.final_snapshot_identifier | |||
apply_immediately = var.apply_immediately | |||
|
|||
dynamic "log_delivery_configuration" { | |||
for_each = var.log_delivery_configuration |
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 convert it to a map (in locals) to prevent updating the whole list if any item changes?
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.
Only two items can be used here, one for each log_type
. We could turn it into a map but i think it would be overkill.
for_each = var.log_delivery_configuration | ||
|
||
content { | ||
destination = lookup(log_delivery_configuration.value, "destination", null) |
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.
are any of these required, or they are all optional?
(if required, we should not provide the default null
value)
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 docs do not say. I haven't looked at the golang code and the test sets every key. I figured I'd err on the side of caution and default to null in case one was optional.
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.
please see comments
/test all |
* Add log_delivery Co-authored-by: cloudpossebot <11232728+cloudpossebot@users.noreply.github.com>
what
log_delivery_configuration
why
references
aws_elasticache_replication_group
Test
Test this out in your infrastructure