We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
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.
0 Votes
Vlad Trofimov posted about 2 years ago Admin 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
0 Votes
1 Comments
Vlad Trofimov posted about 2 years ago Admin 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
0 Votes
Login or Sign up to post a comment