-
-
Notifications
You must be signed in to change notification settings - Fork 672
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
Access Logs should be optional #56
Comments
@lvampa - Typically this would be simple to do but Terraform is not cooperating with how I had this originally in mind (failing branch is here) :
I'm able to work around the problem by providing a dedicated variable for I'll try to release this functionality this week but honestly shipping the ability for someone to not log requests is a somewhat low priority if you catch my drift 😄 . |
Hi, |
Bump, just checking on this. Would love to switch over to using community modules from our own custom cruft, but we have high volume internal ALBs that we do not require logging for. I see some work on this by @mohsen0 but it doesn't look like that work was merged to master or released. Thanks! |
This is an incredibly messy changeset (see the diff) as I expected it would be but this feature request is now fulfilled by #69 and released as 3.4.0. |
Wow thanks for the speedy work @brandoconnor! kudos. Admittedly I don't understand now how the main.tf is all comment block and it seems like has been forked into two different tf files... but presumably that is part of the messyness you are referring to. anyways, thanks! |
Thanks on the kudos. I'd been avoiding this work for a while knowing it'd be kind of gross but it's not so bad I suppose. I broke out the resources into the
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Current Module version -
3.1.0
I apologize ahead of time for dragging this issue back up.
Issue
By including the
access_log
block like this -You are prescribing a certain resource structure instead of letting the module user decide what they want.
Background
Previous related issue - #31
Summarized outcome from issue - make access logs required
Based upon the AWS Documentation -
"Access logging is an optional feature of Elastic Load Balancing that is disabled by default."
Proposal
The text was updated successfully, but these errors were encountered: