Welcome
Login  Sign up
Start a new topic
Answered

Version Control for Leostream configuration

I would like to see an integration with version control implemented in Leostream, whereby the existing configuration (not the state) is committed to git or similar, maybe in XML (if that's easy given the existing API), and I can rollback to a previous configuration as easily as making a configuration change. Database backups are useful and essential, but are no substitute for change tracking and version control, of which the smallest edit should be tracked. Saving any configuration change when version control is enabled should prompt the editor for a commit comment.


Best Answer

Hi Alan,


I have submitted this to the product team to review. Having an exportable configuration that can easily recover policies, protocol plans, locations, etc. would be useful without having to restore the entire database from a backup. I've also added a note about storing these configuration exports for tracking version control.


Best,
Vlad

1 Comment

Answer

Hi Alan,


I have submitted this to the product team to review. Having an exportable configuration that can easily recover policies, protocol plans, locations, etc. would be useful without having to restore the entire database from a backup. I've also added a note about storing these configuration exports for tracking version control.


Best,
Vlad

Login or Signup to post a comment