Closed feich-ms closed 3 years ago
I've investigated this with Fei and we found that, composer does not use authoringRegion and region correctly in some places. Here are the details: We have two kind of luis services in composer: Authoring and Prediction. We should have following luis settings for the two services:
"luis": {
"authoringKey": "",
"authoringRegion":"",
"authoringEndpoint": ""
"endpointKey": "",
"region": "",
"endpoint": "",
},
For local publish, if endpointKey is null or empty, we'll use the authoringKey as the endpointKey, at this time, we should also set region to authoringRegion, and in composer runtime, we should always just take the endpointKey and region to call luis service.
But today, we don't have region setting, and don't set that, which will be confusing and error-prone.
For azure publish, we should also set both settings and use them separately, authoringKey and authoringRegion should be used to create luis applications, endpointKey and region should be used in runtime to call luis service.
But today, when we generate luis.settings.{environment}.{region}.json, we didn't care about the prediciton service binding, just all use the authoringRegion.
I will go through with all the luis region footprints with Fei together to make sure, we have correct logic with luis regions both in composer and cli.
Describe the bug
Luis prediction doesn't work when publishing models to regions out of westus, e.g. westeurope. The luis publishing succeed, but the prediction keep failing due to prediction endpoint key not found.
Version
Main branch
Browser
OS
To Reproduce
Steps to reproduce the behavior:
“” is not a valid LUIS application id.
Expected behavior
The luis model in bot should be able to predict user input
Screenshots
Additional context