Skip to content
This repository has been archived by the owner on Dec 23, 2023. It is now read-only.

Moving deploy to composer #82

Merged
merged 3 commits into from
Oct 8, 2021
Merged

Moving deploy to composer #82

merged 3 commits into from
Oct 8, 2021

Conversation

drguthals
Copy link
Contributor

@drguthals drguthals commented Oct 4, 2021

Lab/Demo: 13 and 14

Fixes #83

Changes/TODO

@drguthals
Copy link
Contributor Author

drguthals commented Oct 4, 2021

When trying to deploy my bot in the Azure Composer lab, I received this error:

Provisioning completed 3 items before encountering a problem. {"name":"CREATE_COSMOSDB_ERROR","message":"Error - The subscription is not registered to use namespace 'Microsoft.DocumentDB'. 
See https://aka.ms/rps-not-found for how to register subscriptions.","stack":"Error\n at new CustomizeError 
(C:\\Users\\Student\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:255547:25)\n at createCustomizeError2 
(C:\\Users\\Student\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:255552:10)\n at AzureResourceMananger.deployCosmosDBResource 
(C:\\Users\\Student\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:256698:13)"}. 
See provision.WeatherBot.log in your bot folder

I'm attempting to proceed without addressing that error first.

@drguthals
Copy link
Contributor Author

It failed to deploy, I'm trying to re-create the Publishing Profile without the optional Azure resources, since I think the error was in CosmosDB.

@drguthals
Copy link
Contributor Author

It failed to deploy, I'm trying to re-create the Publishing Profile without the optional Azure resources, since I think the error was in CosmosDB.

This resulted in a successful provisioning.

@drguthals
Copy link
Contributor Author

drguthals commented Oct 4, 2021

Error still: There was an error sending this message to your bot: HTTP status code ServiceUnavailable

This one was found in the Channels of the Bot blade in Azure.

@drguthals
Copy link
Contributor Author

Ok, I was able to identify the actual error...it's the same zip error 😭

Deploy zip error...service is unavailable

@drguthals
Copy link
Contributor Author

Created an issue in the Bot Composer repo: microsoft/BotFramework-Composer#8724

@drguthals
Copy link
Contributor Author

Deciding to remove bot deployment completely until the deployment is fixed for Framework or Composer.

@drguthals drguthals added bug Something isn't working on-hold labels Oct 8, 2021
@drguthals drguthals self-assigned this Oct 8, 2021
@drguthals drguthals marked this pull request as draft October 8, 2021 18:36
@drguthals drguthals merged commit 26514b4 into master Oct 8, 2021
@drguthals drguthals deleted the moving-deploy-to-composer branch October 8, 2021 19:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working on-hold
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Adding Deployment to Bot Labs
1 participant