BF CLI luis:application:publish --direct flag does not work

[AndyCW]

Versions

What CLI version are you using: @microsoft/botframework-cli/4.9.0-preview.114058 win32-x64 node-v12.16.1 (from daily builds)
What Nodejs version are you using: v12.16.1
What command-line interpreters are you using: Powershell and bash
What OS are you using: Windcows 10 and Ubuntu

Describe the bug

The bf luis:application:publish command includes a flag --direct which, when defined, is meant to publish the specified version directly, rather than to the Staging or Production slots. This flag is ignored - if you issue this command, the response indicates that the version has not been direct published, and instaed ahas been published to Production. This is confirmed by viewing the version on the portal.

To Reproduce

Steps to reproduce the behavior:

1. Create an app and a version.
2. Train the version.
3. At the command line, issue this command:

bf luis:application:publish --direct  --appId=c959c317-4885-486d-a5ac-9678xxxxxxxx --endpoint https://luisdevopsresource-authoringtest.cognitiveservices.azure.com/ --subscriptionKey 16f6ee4329ca4e19a4f9a213xxxxxxxx --versionId 0.2

4. The response comes back:

{
  "versionId": "0.2",
  "isStaging": false,
  "endpointUrl": "https://westus.api.cognitive.microsoft.com/luis/v2.0/apps/c959c317-4885-486d-a5ac-9678xxxxxxxx",
  "region": "westus",
  "assignedEndpointKey": null,
  "endpointRegion": "westus",
  "failedRegions": "",
  "publishedDateTime": "2020-03-30T17:27:30Z",
  "directVersionPublish": false
}

Expected behavior

If you call the REST API directly with Curl, it works and the version is direct version published. This is the behavior I expect.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

[bug]

[munozemilio]

Hi @AndyCW, could you please share the http post you are running with curl? Does it work for you in the portal?

[AndyCW]

This works in the portal.
This is the request:
POST https://luisdevopsresource-authoring.cognitiveservices.azure.com/luis/authoring/v3.0-preview/apps/c49711f8-d7d9-4a2a-8734-f22708d88465/publish HTTP/1.1
Host: luisdevopsresource-authoring.cognitiveservices.azure.com
Content-Type: application/json
Ocp-Apim-Subscription-Key: ••••••••••••••••••••••••••••••••

{
"versionId": "0.1.40",
"directVersionPublish": true
}

IMPORTANT: The JSON response you get back from this call shows the WRONG DATA. It says that the version was NOT direct version published, but this is a red herring. The version HAS in fact been direct version published:

RESPONSE CONTENT:
Pragma: no-cache
Apim-Request-Id: 7518bde5-559e-4e07-9868-f64121db7a5d
Request-Id: 7518bde5-559e-4e07-9868-f64121db7a5d
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Request-Context: appId=cid-v1:26a3540d-a02a-4998-a060-715488fd769b
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store, proxy-revalidate, no-cache, max-age=0, private
Date: Thu, 30 Apr 2020 14:36:44 GMT
Content-Length: 313
Content-Type: application/json; charset=utf-8

{
"versionId": "0.1.40",
"directVersionPublish": false,
"endpointUrl": "https://westus.api.cognitive.microsoft.com/luis/v2.0/apps/c49711f8-d7d9-4a2a-8734-f22708d88465",
"isStaging": false,
"assignedEndpointKey": null,
"region": "westus",
"endpointRegion": "westus",
"publishedDateTime": "2020-04-30T14:36:44Z",
"failedRegions": ""
}

You can confirm that it was successfully direct version published if you issue a prediction request direct to the version endpoint, like this, it works:
https://westus.api.cognitive.microsoft.com/luis/v3.0-preview/apps/c49711f8-d7d9-4a2a-8734-f22708d88465/versions/0.1.40/predict?query=how many days vacation do i have left

Response content
Pragma: no-cache
Apim-Request-Id: 4f707db7-b599-41bb-b39d-a611b82b0d3e
Request-Id: 4f707db7-b599-41bb-b39d-a611b82b0d3e
X-API-Deprecation-Date: 2019-12-01T00:00:00Z
CSP-Billing-Usage: CognitiveServices.LUIS.Transaction|1
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Request-Context: appId=cid-v1:26a3540d-a02a-4998-a060-715488fd769b
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store, proxy-revalidate, no-cache, max-age=0, private
Date: Thu, 30 Apr 2020 14:42:24 GMT
Content-Length: 217
Content-Type: application/json; charset=utf-8

{
"query": "how many days vacation do i have left",
"prediction": {
"normalizedQuery": "how many days vacation do i have left",
"topIntent": "RequestVacation",
"intents": {
"RequestVacation": {
"score": 0.62471354
}
},
"entities": {}
}
}

If you try this prediction request after you have tried to direct version publish with the bf luis cli, it fails with 'not found'