v0.7.0
🚀 Enhancements
Added variable for cloudwatch Full Request and Response Logs: data_trace_enabled @sheilman16 (#43)
Repeat of PR 36 with requested updates from main and to readme.
what
- Added variable
data_trace_enabled
to theaws_api_gateway_method_settings
resource - This change allows for configuration of CloudWatch logging setting "Full Request and Response Logs" available in the AWS UI. [2]
why
The variable logging_level
controls 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 = true
is required in conjunction with logging_level = "INFO"
to enable "Full Request and Response Logs". This is added to the aws_api_gateway_method_settings
resource in the settings
code block [2]:
settings {
logging_level = "INFO"
metrics_enabled = true
data_trace_enabled = true
}
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)
🤖 Automatic Updates
Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#42)
what
- Update workflows (
.github/workflows
) to addissue: write
permission needed by ReviewDogtflint
action
why
- The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @osterman (#41)
what
- Update workflows (
.github/workflows/settings.yaml
)
why
- Support new readme generation workflow.
- Generate banners
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#40)
what
- Install latest GitHub Action Workflows
why
- Use shared workflows from
cldouposse/.github
repository - Simplify management of workflows from centralized hub of configuration