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 Cluster Peering in the service / services API functions #1694

Closed
jcjones opened this issue Jan 5, 2023 · 1 comment · Fixed by #1822
Closed

Support Cluster Peering in the service / services API functions #1694

jcjones opened this issue Jan 5, 2023 · 1 comment · Fixed by #1822

Comments

@jcjones
Copy link

jcjones commented Jan 5, 2023

Consul 1.14 added support for Cluster Peering, and the new peer parameter for the /health API endpoint to access imported services.

It would be natural for consul-template to support the new peer parameter for the service and services API functions. This would allow consul-template to offer imported services in configuration files

The current service function syntax is:

{{ service "<TAG>.<NAME>@<DATACENTER>~<NEAR>|<FILTER>" }}

Perhaps simply double-@s like @@<PEER>, or a character like !<PEER> would suffice and stay short, or add convention for peer=<PEER>?

The code changes for this seem to be mostly in https://github.com/hashicorp/consul-template/blob/main/dependency/health_service.go.

@blake blake linked a pull request Apr 30, 2024 that will close this issue
3 tasks
@blake
Copy link
Member

blake commented Apr 30, 2024

Support for querying peered services was added by #1822.

@blake blake closed this as completed Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants