this value currently controlled by one of the ENV variables.
why this is needed.
we are currently deploying kong in several regions, US, EU, etc.
some APIs are geo DNS aware, some are not, so our default DNS is US only and look like:
api.dns.com, this is displayed in swagger and API Info page.
For geo enabled services we introduced different DNS: geo-api.dns.com and we want geo services to display that.
I think this is trivial change, for the swagger I believe we can already provide base URL.
For the API info page, we probably have to add additional optional field, API DNS and if configured use it, this is kickstarter and portal.
This potentially can be multiply DNS names, each specific to a set of APIs, this gives us ability to change flow policy per API ( deployment, update, etc )
Martin, we can do this, just want to follow up with you, and possibly get a feedback.
this value currently controlled by one of the ENV variables.
why this is needed.
we are currently deploying kong in several regions, US, EU, etc.
some APIs are geo DNS aware, some are not, so our default DNS is US only and look like: api.dns.com, this is displayed in swagger and API Info page.
For geo enabled services we introduced different DNS: geo-api.dns.com and we want geo services to display that.
I think this is trivial change, for the swagger I believe we can already provide base URL. For the API info page, we probably have to add additional optional field, API DNS and if configured use it, this is kickstarter and portal.
This potentially can be multiply DNS names, each specific to a set of APIs, this gives us ability to change flow policy per API ( deployment, update, etc )
Martin, we can do this, just want to follow up with you, and possibly get a feedback.