Publishing a bot for the first time through creation of a publishing profile doesn't publish bot to app service

[darrenj]

Describe the bug

When creating a new bot, publishing to Azure through creation of a Publishing profile doesn't appear to push bits onto the App-Service

Version

1.4.0.nightly-233315

Browser

• Electron distribution
• Chrome
• Safari
• Firefox
• Edge

OS

• macOS
• Windows
• Ubuntu

To Reproduce

Steps to reproduce the behavior:

1. Create a new project (basic assistant)
2. Create a publishing profile and publish
3. Go to created ABS resource and test in webchat (doesn't work)
4. go to kudo and inspect published files (none)

Expected behavior

1. Bot published and works in Azure

Screenshots

Additional context

• This could be down to an issue that the Bot in question isn't able to start locally (see runtime.setSkillManifest is not a function error when starting a new Basic Assistant project #6823). Perhaps as part of publishing/provisioning it's also hitting this error and silently carrying on. Provisioning was reported as being successful , so if it is indeed this issue causing the issue then provisioning should not report success.

[pavolum]

@GeoffCoxMSFT This is expected behavior and proposed solution is deep link outlined in #6836

[sgellock]

Shiproom - @GeoffCoxMSFT can you look at what it would take to add deployment to the create pub profile flow, so we deploy. talk with @benbrown as well, as risk here could be high

[GeoffCoxMSFT]

We can't put publishing within the provisioning wizard because the provisioning wizard closes when provisioning starts. The server code sends notifications back to main UI. The main UI would have to watch for successful provisioning and detect that it is a new profile. Then it would have to use a special navigation to the publishing page and start the publishing process. In the multi-bot scenario, I don't thing this process would know which bots to select for publishing as we don't know that creating a profile for one bot means that other bots are ready to be published or if the user is really ready to publish the bot with the new profile.

[cwhitten]

We've got options here, but before we can move forward on engineering we need an experience review to clarify the UX on initial provision + optional publish. Assigning @Dewain27 to push this forward and moving to R15 for now.