为Azure Bot Service设置插槽或多个环境 [英] Setting up slots or multiple environments for Azure Bot Service

问题描述

我正在使用Azure Bot Service开发Microsoft Bot，希望为我们设置不同的环境或插槽以进行质量检查，开发和登台，就像我们在azure应用程序服务中的工作方式一样.

I am working on developing a Microsoft Bot using Azure Bot Service, in that want to set up different environments or slots for QA, Dev, Staging like how we do in azure app services.

在设置中，我没有找到部署插槽"选项，但是在设置下，每个设置都有插槽设置"复选框，这意味着我们也可以在Azure Bot Service中配置插槽，还是我必须为每个Bot Service创建多个Bot Service资源环境?

In settings I did not find Deployment Slots option but under settings each setting have Slot Setting check box, is that means can we configure slots in Azure Bot Service as well or do I have to create multiple Bot Service resources each one for each environment?

推荐答案

您将要为每种环境(例如，一个用于开发环境，一个用于生产环境)创建单独的机器人.

You'll want to create separate bots, for each environment (i.e. one for Dev and one for Production).

配置和使用分段部署的过程大致如下:

The process to configure and work with a staging deployment looks generally like this:

1. 在您的订阅中创建两个机器人应用程序，其中一个用于 生产代码和暂存代码.
2. 创建一个部署源(如果您还没有的话).这 该示例使用GitHub.
3. 对于生产功能应用程序，请完成设置"中的上述步骤 连续部署并将部署分支设置为主服务器 GitHub存储库的分支.
4. 选择部署分支
5. 对登台功能应用重复此步骤，但是选择 暂存分支，而不是在您的GitHub存储库中.如果您的部署 源不支持分支，请使用其他文件夹.
6. 对登台分支或文件夹中的代码进行更新，然后 验证这些更改是否反映在登台部署中.
7. 测试之后，将登台分支中的更改合并到主数据库中 分支.这将触发部署到生产功能应用程序. 如果您的部署源不支持分支，请覆盖 生产文件夹中的文件以及暂存中的文件 文件夹.

1. Create two bot apps in your subscription, one for the production code and one for staging.
2. Create a deployment source, if you don't already have one. This example uses GitHub.
3. For your production function app, complete the above steps in Set up continuous deployment and set the deployment branch to the master branch of your GitHub repo.
4. Choose deployment branch
5. Repeat this step for the staging function app, but choose the staging branch instead in your GitHub repo. If your deployment source doesn't support branching, use a different folder.
6. Make updates to your code in the staging branch or folder, then verify that those changes are reflected in the staging deployment.
7. After testing, merge changes from the staging branch into the master branch. This will trigger deployment to the production function app. If your deployment source doesn't support branches, overwrite the files in the production folder with the files from the staging folder.

这篇关于为Azure Bot Service设置插槽或多个环境的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！