Added variable for cloudwatch Full Request and Response Logs: data_trace_enabled #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Repeat of PR 36 with requested updates from main and to readme.
what
data_trace_enabledto theaws_api_gateway_method_settingsresourcewhy
The variable
logging_levelcontrols CloudWatch log setting in the AWS UI for OFF, INFO, and ERROR, but doesn't include an option for "Full Request and Response Logs". In the AWS UI for API GW, there's an additional option, "Full Request and Response Logs", as shown in the screenshot:According to terraform documentation, the variable
data_trace_enabled = trueis required in conjunction withlogging_level = "INFO"to enable "Full Request and Response Logs". This is added to theaws_api_gateway_method_settingsresource in thesettingscode block [2]:references
[1] Terraform resource:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/api_gateway_method_settings
[2] Closed Issue with Terraform citing solution
hashicorp/terraform-provider-aws#35863 (comment)