We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.
We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.
Thanks for collaborating with us!
`chef-automate` should support the creation of multiple full backups that are self contained and do not depend on other backups to have successfully exported their data.
The first backup created with `chef-automate backup create` is a full backup, but for subsequent backups, chef-automate does not export all of its data and instead creates an incremental snapshot of ElasticSearch/OpenSearch data. This essentially means that no matter how many times we run `chef-automate backup create`, it will only produce a single backup with multiple restore points (there is only one copy of our data). As we recently discovered, the corruption of a single file from our oldest backup can render all backups created with chef-automate unrecoverable.