Glue Crawler role accepts ARN but returns plan difference

[bflad]

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 "me too" comments, 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 Version

• terraform v0.11.10
• terraform-provider-aws v1.41.0

Affected Resource(s)

• aws_glue_crawler

Terraform Configuration Files

resource "aws_glue_crawler" "test" {
  # ... other configuration ...

  role = "${aws_iam_role.test.arn}"
}

Debug Output

--- FAIL: TestAccAWSGlueCrawler_DynamodbTarget (18.09s)
    testing.go:538: Step 0 error: After applying this step, the plan was not empty:

        DIFF:

        UPDATE: aws_glue_crawler.test
          role: "tf-acc-test-5817417459117994664" => "arn:aws:iam::187416307283:role/tf-acc-test-5817417459117994664"

Expected Behavior

Terraform should report no difference in the attribute.

Actual Behavior

Terraform reports a difference in the attribute.

Steps to Reproduce

Reproducible via acceptance testing update and run:

1. Change .name to .arn at https://github.com/terraform-providers/terraform-provider-aws/blob/5aaf64f80342d36f55185b778a372bf50175813d/aws/resource_aws_glue_crawler_test.go#L926
2. make testacc TEST=./aws TESTARGS='-run=TestAccAWSGlueCrawler_DynamodbTarget'

References

• Fix bad advice on using ".name" property of Role while ignoring path #6285 (comment)

[bflad]

Pull request submitted: #6293

[bflad]

The fix for this has been merged into master and will release with version 1.42.0 of the AWS provider, likely today or tomorrow.

[bflad]

This has been released in version 1.42.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!