aws_cloudwatch_event_rule - error reading CloudWatch Events Rule - unexpected format for ID

[sufiyanghori-apt]

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 v1.0.4
provider registry.terraform.io/hashicorp/aws v3.54.0

Affected Resource(s)

• aws_cloudwatch_event_rule

Terraform Configuration Files

resource "aws_cloudwatch_event_rule" "buildkite-secret-scanner-events" {
  name          = "test"
  event_bus_name = "aws.partner/foo.com/foo/18554d09-58ff-aa42-ba9c-c4c33899006f"
  event_pattern = <<PATTERN
{
  "detail-type": [ "test" ]
}
PATTERN
}

Debug Output

Panic Output

Expected Behavior

Event rule should be created.

Actual Behavior

Terraform fails,

#16973 (comment)

error reading CloudWatch Events Rule (aws.partner/appflow/salesforce.com/xxx/foo-eventbus/bar-rule): unexpected format for ID ("aws.partner/appflow/salesforce.com/xxx/foo-eventbus/bar-rule"), expected / or "

Steps to Reproduce

1. terraform apply

Important Factoids

References

#16973 (comment)

• #0000

[ewbankkit]

Related:

• aws_cloudwatch_event_target does not support cross-account Event Bus #8759
• aws_cloudwatch_event_rule creates rules in other accounts but fails to read them with error unexpected format for ID #19234

[ewbankkit]

@sufiyanghori-apt Thanks for raising this issue.
This should have been fixed in #19072, released in v3.39.0 of the Terraform AWS Provider.
Does your event bus name contain any "special" characters?

[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!

[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.