Forum Discussion
Moving a bot from Draft to Production
I would like to know how you handle moving a Healthbot from Draft to Production. I don't know if there is a migration solution within Healthbot. As an example, I have a Healthbot in Production but I want to make some changes to it but I don't want those changes to go into Production until I am ready. The way I believe it works today, is that as soon as I save the Healthbot changes, those changes are in Production. My thought is that I have to create a clone of my production bot and then make changes to the clone. When I am ready for Production, I just change the "Scenario ID"s between the Production one and the clone one. The Clone will now have my production "Scenario ID". I think this will work but just checking with the community if there is a better way.
- GregoryLisiak
Microsoft
You might want to consider a slightly different approach. Not sure changing the Scenario IDs is your best route. You might want to consider setting up a separate Free Health Bot instance to do your development work in which would allow you to keep the same Scenario ID in your development environment. When you are ready to promote your code, you could export the scenario and import it into the production environment. By doing this, you would not break any active connections to the bot and new bot connections would be based on the new code. Although dated, here is a post that talks about one method to manage code across multiple environments. https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/health-bot-instance-management-and-version-control-best/ba-p/1240487GregoryLisiak, thanks for the reply. I was looking for something like this but couldn't find it. Appreciate the insight and the link.
