Provider produced inconsistent final plan / an invalid new value for .tags_all when resource tag has an apply-time value and provider default_tags are in use

[bassmanitram]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

• Terraform v0.12.31
• AWS Provider v3.75.1

Affected Resource(s)

• aws_cloudwatch_log_group
• aws_ssm_parameter
• aws_api_stage
• aws_apigatewayv2_stage
• ...

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

provider "aws" {
	region = "us-east-1"
	version = "~>3.0" 
	default_tags {
		tags = {
			Type = "Test CloudwatchLog Group"
		}
	}
}

resource "random_string" "apply_time_tag_value" {
  length  = 10
  special = false
  upper = false
}

resource "aws_cloudwatch_log_group" "my_cloudwatch_log_group" {
	name = "/test-cw-log-group"
	tags = {
		ApplyTimeValue = random_string.apply_time_tag_value.result
	}
}

Expected Behavior

Successful apply

Actual Behavior

Error: Provider produced inconsistent final plan

When expanding the plan for aws_cloudwatch_log_group.my_cloudwatch_log_group
to include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for .tags_all: new
element "Name" has appeared.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Steps to Reproduce

1. terraform init
2. terraform apply

[bassmanitram]

Sorry - this appears to be a duplicate of many similar reports, the most commented-on being #19583

[bassmanitram]

Duplicate of #19583

[github-actions]

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.