Skip to content
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

[AWS SDK for Go Migration] IoT Events Service #36172

Closed
Tracked by #32976
breathingdust opened this issue Mar 6, 2024 · 4 comments · Fixed by #37152
Closed
Tracked by #32976

[AWS SDK for Go Migration] IoT Events Service #36172

breathingdust opened this issue Mar 6, 2024 · 4 comments · Fixed by #37152
Labels
aws-sdk-go-migration Issues that are related to the providers migration to AWS SDK for Go v2. service/iotevents Issues and PRs that pertain to the iotevents service.
Milestone

Comments

@breathingdust
Copy link
Member

Description

To align with the dates described on #32976 the IoT Events Service requires migration to rely fully on AWS SDK for Go v2. This change should be mechanical in nature and not introduce any behavior changes.

The maintainer team will be working on these migrations but as always, help from the community is always appreciated. We would require passing acceptance tests for the entire set of resources being migrated. (We will also validate on review)

For further information about the migration, please see the parent issue #32976.

Resources In Scope for Migration


Data Sources In Scope for Migration


References

@breathingdust breathingdust added aws-sdk-go-migration Issues that are related to the providers migration to AWS SDK for Go v2. service/iotevents Issues and PRs that pertain to the iotevents service. labels Mar 6, 2024
Copy link

github-actions bot commented Mar 6, 2024

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.

Copy link

github-actions bot commented Jul 2, 2024

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

Copy link

github-actions bot commented Jul 5, 2024

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

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Copy link

github-actions bot commented Aug 7, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
aws-sdk-go-migration Issues that are related to the providers migration to AWS SDK for Go v2. service/iotevents Issues and PRs that pertain to the iotevents service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant