Skip to content

Implement hypercore_remote_cluster_connection data source #23

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

Merged
merged 2 commits into from
Apr 2, 2025

Conversation

anazobec
Copy link
Collaborator

@anazobec anazobec commented Apr 1, 2025

This PR implements the hypercore_remote_cluster_connection which is intended to be used alongside the hypercore_replication resource where the user will list remote cluster connections on HC3, choose one and use it with that replication resource.

This can also be tested using the local/main.tf.

For more info check the regenerated docs.

@anazobec anazobec requested a review from justinc1 April 1, 2025 13:23
@anazobec anazobec self-assigned this Apr 1, 2025
anazobec added 2 commits April 2, 2025 11:14
* Added a new data source - `hypercore_remote_connection`
* Modified `ListRecords` to also filter recursively if specified so -
this is useful for filtering through nested maps which was needed here
@justinc1 justinc1 force-pushed the hypercore_remote_connection_data_source branch from bcd3170 to 5d89d11 Compare April 2, 2025 09:14
Copy link
Collaborator

@justinc1 justinc1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, tested, works, ty, great :)

@justinc1 justinc1 merged commit 359bd6b into main Apr 2, 2025
6 checks passed
@justinc1 justinc1 deleted the hypercore_remote_connection_data_source branch April 2, 2025 09:17
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 2, 2025
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 this pull request may close these issues.

2 participants