bf luis:cross-train should output target recognizer info

[gabog]

Currently luis:cross-train crawls a given folder for lu and qna files and outputs the found files to another folder but it doesn't persist any information on what recognizer should be used to build, train and publish that file.

In some senarios, you can have a bot that have dialogs that use LUIS recognizers and dialogs that use an orchestrator recognizer. With the current output of luis:cross-train we can't tell if we need to call luis:build or orchestrator:build.

If this change is implemented, we will also need to modify luis:build and orchestrator:build to look at this information when crawling the files for training.

Note (5/11/2021): One possible solution would be for cross-train to generate luconfig files like I did for CI/CD, it should generate one config file for each recgonizer listing the LU models for each one of them.

[gabog]

Hi @scheyal, ping me if you need more details, it would be good to address this in R14

[scheyal]

Status: consulting with Dong. Update soon.

[scheyal]

Update: Scheduled a meeting w/ Dong & Gabo. Proposed that the fix should come by scanning the .dialog files (i.e. get it from the source, don't require repeat in another source).

[scheyal]

Meeting summary:

• We will create new "discover" command in LUIS & Orchestrator BF CLI commands that will discover and produce listings of language assets in a way that would be consumable by the corresponding build commands.
• @boydc2014 will follow up next.
• This work will be scheduled for R15 since it can be risky, and we have an intermediate workaround.

[munozemilio]

@boydc2014 is this still valid? will this be released in R15?

[cosmicshuai]

Maybe we can move it to R16