After rebuilding a new jambonz web+monitoring server instance, and updating the Cloudformation stack, all the data in the RDS database is reset to default when the new instance is launched.
This is very annoying on a production cluster since it wipes all the cpaas configuration.
In the jambonz-scalable-medium.yaml template, there should be a condition before running the "seeding database.." code block.
@ajukes trying to recall how we handled this problem earlier. I think we had to create a new CF that did not include the database (?). I'm not sure if that is the best way though..
After rebuilding a new
jambonz web+monitoring
server instance, and updating the Cloudformation stack, all the data in the RDS database is reset to default when the new instance is launched.This is very annoying on a production cluster since it wipes all the cpaas configuration.
In the
jambonz-scalable-medium.yaml
template, there should be a condition before running the"seeding database.."
code block.