Before using the NLU.DevOps tool, you need to supply Dialogflow secrets and endpoint configuration to be able to test a Dialogflow model. The values are configured through Microsoft.Extensions.Configuration
(i.e., an appsettings.local.json
file or environment variables).
At a minimum to get started, you must supply the Dialogflow client authentication key with relevant permissions, as well as the Dialogflow project ID.
{
"dialogflowClientKeyPath": "...",
"dialogflowProjectId": "..."
}
This will allow you to call the test
sub-command for Dialogflow (see Testing an NLU model for more details).
Options to consider for testing a Lex bot include:
(Optional) Google credential path for authenticating the Dialogflow client.
Optional for test
. If not supplied, dialogflowClientKeyJson
must be specified.
(Optional) Google credential JSON for authenticating the Dialogflow client.
Optional for test
. If not supplied, dialogflowClientKeyPath
must be specified.
Dialogflow project ID.
Required for test
.
(Optional) Dialogflow session ID.
Optional for train
. If not supplied, a random GUID is selected for the session ID for each utterance test.