reverse-proxy icon indicating copy to clipboard operation
reverse-proxy copied to clipboard

Why is the destination of a cluster an object instead of an array in forwarding configuration

Open tengfei8771 opened this issue 1 month ago • 3 comments

The current downstream forwarding configuration structure is as follows: "Clusters": { "cluster1": { "Destinations": { "destination1": { "Address": "https://example.com/" } } } } What is the reason for setting the structure of Destination as an object instead of an array

tengfei8771 avatar Nov 14 '25 08:11 tengfei8771

I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):

  • https://github.com/dotnet/yarp/issues/279

MihuBot avatar Nov 14 '25 08:11 MihuBot

Just because the destinations have unique IDs for each cluster (it's a dictionary), and they're unordered. Is it causing you any problems?

MihaZupan avatar Nov 14 '25 08:11 MihaZupan

Just because the destinations have unique IDs for each cluster (it's a dictionary), and they're unordered. Is it causing you any problems?

It's nothing.Just curious about the data structure

tengfei8771 avatar Nov 14 '25 08:11 tengfei8771