Why is the destination of a cluster an object instead of an array in forwarding configuration
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
I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):
- https://github.com/dotnet/yarp/issues/279
Just because the destinations have unique IDs for each cluster (it's a dictionary), and they're unordered. Is it causing you any problems?
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