In this tutorial you will learn how to manage deployments of bots between environments in the ServisBOT Platform.
ServisBOT provides all clients with a staging and production organization.
It is recommended to lock down access to the production environment and only allow access to the deployment and debug teams. Changes can be done and tested in staging, and then deployed using our tooling.
Development can begin following one of our getting started tutorials.
Secrets are not exported or migrated between orgs, but since they are referenced by alias, all that is needed is to make sure that secrets exist in both orgs with the same alias.
Inside the BaaS that uses secrets, there will be a
It is assumed that your staging and product environments will require entirely different secrets, all that needs to match is the alias.
sb-cli bot download BOTNAME
This will include all workers, BaaS, intents, slots, and the default endpoint related to the bot.
sb-cli bot upload .
. just denotes current directory.
You should be all set to test your bot in the platform now.