Closed ericchansen closed 5 years ago
@ericchansen - Thanks so much, I totally agree these steps are a little too hard and were sadly needed as we were awaiting automation support. The good news that this weekend we are publishing a whole new set of documentation and bits that automate all of what you say above - would love your comments on that (currently in 4.4 branch about to get merged)
Project
Name: Virtual Assistant
Language: C#
Description
I'm following the instructions in https://github.com/Microsoft/AI/blob/master/docs/virtual-assistant/csharp/gettingstarted.md.
The documentation states, "The first command shown below will retrieve the appId (ApplicationId) and appPassword (Client Secret) that you need to complete this step." The documentation is referencing
msbot get production --secret YOUR_SECRET
.It's not clear what is meant by
YOUR_SECRET
. I imagine that that this could be the .bot file secret or the secret that's created with the application registration in the Azure Portal.Running
msbot get production --secret BOT_FILE_SECRET
(which is how the documentation should be written) returnsappPassword
isn't returned. This makes the next step (shown below) particularly confusing.The documentation isn't explicit when referencing the many secrets and IDs.
appPassword
. These are all accompained by 3 additionalappId
.In the command above,
YOUR_APPLICATION_PASSWORD
could be the secret retrieved from the application registration or it could be one of the 3 inside the .bot file. Similarly,YOUR_APPLICATION_ID
could be the ID of the application registration or it could be one of the 3 found inside the .bot file.To Reproduce
Follow steps in https://github.com/Microsoft/AI/blob/master/docs/virtual-assistant/csharp/gettingstarted.md. Note that I had to manually create my application registration and retrieve my application ID and password/secret to avoid
ERROR: Unable to provision MSA id automatically. Please pass them in as parameters and try again
.Expected behavior
I expect to run
and get a response that clearly states what secret to use in
Alternatively, if
msbot
is functioning as intended by returning$appSecret
, make the documentation explicit such that users can follow it without prior knowledge.Either way, it would be great if the documentation was more explicit when referencing the many secrets, passwords and IDs that are created and/or used throughout.
Screenshots
None for now. Can update as needed.
Additional context
None for now. Can update as needed.