[Bug]: Not able to delete the tracing_config block.

[NishaSubramani-stats]

Terraform Core Version

1.3.6

AWS Provider Version

4.40.0

Affected Resource(s)

aws lambda function

Expected Behavior

Tracing config needs to be disabled for lambda once we remove the block from terraform.

Actual Behavior

When tracing config is removed it's not reflecting any changes in the infrastructure.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource “aws_lambda_function” “xxx” {
  function_name = “xxx”
  role = “role”
  handler = “lambda_function.main”
  runtime = “python3.9”
  timeout = 300
  memory_size = 1792
  layers = [xray_lambda_layer]
  tracing_config {
      mode = “Active”
  }
}

Steps to Reproduce

1. Deploy lambda with tracing_config block enabling the tracing mode: "Active"
2. Remove the tracing block
3. Do terraform plan
4. The plan doesn't include disabling the tracing

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

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]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!