[NET-9468, NET-9901] Use /v1/exported-services instead of config entry list for exportedServices func #1948
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
/v1/config/exported-services
endpoint (docs) -- which is currently used for theexportedServices
func -- simply returns the config entries as they exist. This means that a wildcarded export, for example, will simply return the wildcard.In contrast, the
/v1/exported-services
endpoint (docs) -- introduced in hashicorp/consul#20015 -- resolves wildcards to the resulting list of exported service names and resolves sameness groups to the resulting list of peers and partitions.With this change, wildcard exports are now expanded out to the full list of exported services instead of just
*
for the service name:Note
This change means that users must be on Consul 1.17.3+ in order to use the
exportedServices
function (docs)