service/dms: add data source for dms_replication_instance

[snypelife]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment 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 pull request followers and do not help prioritize the request

Relates to #12713

Release note for CHANGELOG:

* data/aws_dms_replication_instance: Adds data source for DMS Replication instance

Output from acceptance testing:

I currently don't have authorization to run the acceptance tests under my companies account 😞

[snypelife]

Sorry, I know it's only a single data source, instead of all of them for DMS. I'm fairly unfamiliar with Go, and I wanted to keep the pull request as small as possible to make reviewing easier.

[elijah-ward]

Nice work @snypelife

[stpierre]

What's blocking this? This is a pretty significant gap and we'd love for it to be closed.

[zhelding]

Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding.

Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single aws directory to a large number of separate directories in internal/service, each corresponding to a particular AWS service. This separation of code has also allowed for us to simplify the names of underlying functions -- while still avoiding namespace collisions.

We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author.

For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000.

For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide.

[snypelife]

Hey @zhelding thank you for the heads up on the refactor that went in. I've updated my fork and rebased the PR to get it to a merge-able state.

[snypelife]

Heyo! Any uptake on this by any chance? I know it's probably not the most requested feature, but it's intentionally small to make review and acceptance (hopefully) easier.

Thanks!

[nam054]

Thank you for contributing! 🚀

[nam054]

> make testacc TESTARGS='-run=TestAccDMSReplicationInstanceDataSource_basic' PKG=dms
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/dms/... -v -count 1 -parallel 20  -run=TestAccDMSReplicationInstanceDataSource_basic -timeout 180m
=== RUN   TestAccDMSReplicationInstanceDataSource_basic
=== PAUSE TestAccDMSReplicationInstanceDataSource_basic
=== CONT  TestAccDMSReplicationInstanceDataSource_basic
--- PASS: TestAccDMSReplicationInstanceDataSource_basic (883.52s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/dms        886.578s

[snypelife]

🎉 Thanks for merging this @nam054!

[github-actions]

This functionality has been released in v4.66.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!

[github-actions]

I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.