Hi there, We've spotted a major regression on updating to Go 16.7, in that it appears backups no longer capture the history of a pipeline. When we restore a backup, we lose all pipeline history, and all pipelines instantly restart, including ones which were previously suspended.
Our deployment pattern for Go follows the "Phoenix server" pattern, in that all boots happen from a golden master, and then on boot the most recent backup is restored in order to restore configurations, etc, so the ability to restore pipeline history is a crucial part of our workflow. Is this a known issue, or a new one? Or has the backup/restore procedure changed (although we still appear to be following the procedure in the documentation)? Regards, *Chris Northwood* Senior Technologist, UX BBC Research & Development, Dock House, 5th Floor, MediaCityUK, Salford M50 2LH -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
