TI API: destination EAS IP address #294
Labels
enhancement
Suggesting ideas for new API features or questions on directions for API evolution
Fixed
Traffic Influence API
Problem description
The main exposed Intent is: "activate the optimal routing for the closest EAS instance". How to "point" to that Instance is not currently in scope. Usually that information is already known by the Application, because the EAS Instance was deployed via the Edge Cloud APIs but maybe, for some reason, also related to the network, the chosen EAS, in that very moment, could not be the one retrieved by the other EdgeCloud APIs. For this reason we should provide back the EAS IP address. This should solve any problem related to the Client Application targeting the right EAS Instance and it will be clear for the Developer what to expect.
Possible evolution
Add the EAS IP address in the TI API callback response to the TI API Consumer
Alternative solution
Just relay on the usage of FQDN with EDGE DNS providing the EAS Instance IP: #293
Additional context
#293 (comment)
#293
The text was updated successfully, but these errors were encountered: