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

[Bug]: aws_cloudwatch_log_group new property log_group_class forces replacement #34924

Closed
raphael-ratepay opened this issue Dec 14, 2023 · 3 comments
Labels
bug Addresses a defect in current functionality. service/logs Issues and PRs that pertain to the logs service.

Comments

@raphael-ratepay
Copy link

raphael-ratepay commented Dec 14, 2023

Terraform Core Version

v1.4.4

AWS Provider Version

5.30

Affected Resource(s)

aws_cloudwatch_log_group

Expected Behavior

provider update should not replace log_groups

Actual Behavior

terraform tries to replace the log_groups

Relevant Error/Panic Output Snippet

Terraform plan generates the following output:


 resource "aws_cloudwatch_log_group" "documentdb_cluster_audit_log_group" {
      ~ arn               = "arn:aws:logs:eu-central-1:123456789012:log-group:/aws/docdb/audit" -> (known after apply)
      ~ id                = "/aws/docdb/audit" -> (known after apply)
      + log_group_class   = "STANDARD" # forces replacement
        name              = "/aws/docdb/audit"
      + name_prefix       = (known after apply)

Terraform Configuration Files

resource "aws_cloudwatch_log_group" "audit_logs" {
  name = "/aws/docdb/audit"
}

Steps to Reproduce

  • deploy the log-group with version < 5.30
  • update provider to latest
  • run terraform plan

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

@raphael-ratepay raphael-ratepay added the bug Addresses a defect in current functionality. label Dec 14, 2023
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/logs Issues and PRs that pertain to the logs service. label Dec 14, 2023
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Dec 14, 2023
@ewbankkit ewbankkit removed the needs-triage Waiting for first response or review from a maintainer. label Dec 14, 2023
@ewbankkit
Copy link
Contributor

Fixed via #34812.

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/logs Issues and PRs that pertain to the logs service.
Projects
None yet
Development

No branches or pull requests

2 participants