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

Support external endpoint ARNs #71

Closed
kellenanker7 opened this issue Sep 8, 2024 · 3 comments · Fixed by #72
Closed

Support external endpoint ARNs #71

kellenanker7 opened this issue Sep 8, 2024 · 3 comments · Fixed by #72

Comments

@kellenanker7
Copy link
Contributor

kellenanker7 commented Sep 8, 2024

Is your request related to a new offering from AWS?

  • No ❌

Is your request related to a problem? Please describe.

Replication tasks in this module only support endpoints that are also created by the same instance of the module. They do not accept source_endpoint_arn nor target_endpoint_arn.

Describe the solution you'd like.

I would like to be able to supply source_endpoint_arn and target_endpoint_arn to aws_dms_replication_config and aws_dms_replication_task created by this module. This allows for reusing endpoints across instances of this module, rather than requiring duplicate endpoints for every data source/target.

Describe alternatives you've considered.

There are no alternatives to the functionality restricted by this module, besides building the aws_dms_replication_config and aws_dms_replication_task outside the module.

Additional context

@kellenanker7 kellenanker7 changed the title Support external endpoint names/IDs Support external endpoint ARNs Sep 8, 2024
@bryantbiggs
Copy link
Member

sounds like a good first issue if you want to open a PR

@antonbabenko
Copy link
Member

This issue has been resolved in version 2.3.0 🎉

Copy link

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 Oct 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants