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.
Log into your staging organization using the ServisBOT CLI and download a definition.
sb-cli bot download BOTNAME
You will also need to download the definition of your preferred endpoint. Remember that since endpoints control which domains your bot can appear on, you will need to ensure this is accurate for each env.
sb-cli endpoint describe endpointalias -o -q > endpoint.alias.json
alias in the above command with the alias for your endpoint.
Re-upload the bot Definitions
sb-cli bot upload .
. just denotes current directory.
3. Import your endpoint after properly configuring it.
sb-cli endpoint create endpoint.alias.json
Make after the first time you will just need to update the endpoint. Adjust the command to
sb-cli endpoint update endpoint.alias.json
You should be all set to test your bot in the platform now.