Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package velero for openSUSE:Factory checked in at 2023-10-06 21:14:37 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/velero (Old) and /work/SRC/openSUSE:Factory/.velero.new.28202 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "velero" Fri Oct 6 21:14:37 2023 rev:18 rq:1116065 version:1.12.0 Changes: -------- --- /work/SRC/openSUSE:Factory/velero/velero.changes 2023-09-12 21:03:46.750092727 +0200 +++ /work/SRC/openSUSE:Factory/.velero.new.28202/velero.changes 2023-10-06 21:17:33.826633630 +0200 @@ -1,0 +2,45 @@ +Fri Sep 22 08:29:04 UTC 2023 - ka...@b1-systems.de + +- Update to version 1.12.0: + very big changelog, please find it here: + https://github.com/vmware-tanzu/velero/releases/tag/v1.12.0 + + * Breaking changes + - Prior to v1.12, the parameter uploader-type for Velero + installation had a default value of "restic". However, + starting from this version, the default value has been + changed to "kopia". This means that Velero will now use Kopia + as the default path for file system backup. + - The ways of setting CSI snapshot time have changed in v1.12. + First, the sync waiting time for creating a snapshot handle + in the CSI plugin is changed from the fixed 10 minutes into + backup.Spec.CSISnapshotTimeout. The second, the async waiting + time for VolumeSnapshot and VolumeSnapshotContent's status + turning into ReadyToUse in operation uses the operation's + timeout. The default value is 4 hours. + - As from Velero helm chart v4.0.0, it supports multiple BSL + and VSL, and the BSL and VSL have changed from the map into a + slice, and this breaking change is not backward compatible. + So it would be best to change the BSL and VSL configuration + into slices before the Upgrade. + - Prior to v1.12, deleting the Velero namespace would easily + remove all the resources within it. However, with the + introduction of finalizers attached to the Velero CR + including restore, dataupload, and datadownload in this + version, directly deleting Velero namespace may get stuck + indefinitely because the pods responsible for handling the + finalizers might be deleted before the resources attached to + the finalizers. To avoid this issue, please use the command + velero uninstall to delete all the Velero resources or ensure + that you handle the finalizer appropriately before deleting + the Velero namespace. + + * Limitations/Known issues + The Azure plugin supports Azure AD Workload identity way, but + it only works for Velero native snapshots. It cannot support + filesystem backup and snapshot data mover scenarios. + + * Upgrading + https://velero.io/docs/v1.12/upgrade-to-1.12/ + +------------------------------------------------------------------- Old: ---- velero-1.11.1.tar.gz New: ---- velero-1.12.0.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ velero.spec ++++++ --- /var/tmp/diff_new_pack.rYVx46/_old 2023-10-06 21:17:35.310689530 +0200 +++ /var/tmp/diff_new_pack.rYVx46/_new 2023-10-06 21:17:35.314689681 +0200 @@ -17,7 +17,7 @@ Name: velero -Version: 1.11.1 +Version: 1.12.0 Release: 0 Summary: Backup program with deduplication and encryption License: Apache-2.0 ++++++ _service ++++++ --- /var/tmp/diff_new_pack.rYVx46/_old 2023-10-06 21:17:35.346690886 +0200 +++ /var/tmp/diff_new_pack.rYVx46/_new 2023-10-06 21:17:35.346690886 +0200 @@ -5,7 +5,7 @@ <param name="exclude">.git</param> <param name="versionformat">@PARENT_TAG@</param> <param name="versionrewrite-pattern">v(.*)</param> - <param name="revision">v1.11.1</param> + <param name="revision">v1.12.0</param> <param name="changesgenerate">enable</param> </service> <service name="recompress" mode="manual"> ++++++ _servicedata ++++++ --- /var/tmp/diff_new_pack.rYVx46/_old 2023-10-06 21:17:35.366691640 +0200 +++ /var/tmp/diff_new_pack.rYVx46/_new 2023-10-06 21:17:35.366691640 +0200 @@ -1,6 +1,6 @@ <servicedata> <service name="tar_scm"> <param name="url">https://github.com/vmware-tanzu/velero</param> - <param name="changesrevision">bdbe7eb242b0f64d5b04a7fea86d1edbb3a3587c</param></service></servicedata> + <param name="changesrevision">7112c62e493b0f7570f0e7cd2088f8cad968db99</param></service></servicedata> (No newline at EOF) ++++++ velero-1.11.1.tar.gz -> velero-1.12.0.tar.gz ++++++ /work/SRC/openSUSE:Factory/velero/velero-1.11.1.tar.gz /work/SRC/openSUSE:Factory/.velero.new.28202/velero-1.12.0.tar.gz differ: char 23, line 1 ++++++ vendor.tar.gz ++++++ /work/SRC/openSUSE:Factory/velero/vendor.tar.gz /work/SRC/openSUSE:Factory/.velero.new.28202/vendor.tar.gz differ: char 5, line 1
