-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Issue 16973 - allow for ARNs and partner event bus names #18383
Issue 16973 - allow for ARNs and partner event bus names #18383
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @mdragilev 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTING guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
Hi @mdragilev 👋 Thank you for submitting this. It appears this was resolved with #16815, which was released yesterday with version 3.34.0 of the Terraform AWS Provider. |
Actually, my bad, this is for ARNs as well. I'm going to assign this to @gdavison who is most familiar here. |
This was resolved by #18143, which will be released in v3.36.0 later this week |
This fixed the Eventbus name error but now I get error while setting ID - "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 " |
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! |
Updated to allow partner names for the AWS Event Bridge as well as allow to use ARNs in place of event bridge names as that works with the AWS CLI.
Community Note
Closes #16973
Output from acceptance testing: