plugin api: bump api version and age
Changes for version 11: * Allow declaring storage features via plugin data. * Introduce new_backup_provider() plugin method. * Allow declaring sensitive properties via plugin data. See the api changelog file for details. Signed-off-by: Fiona Ebner <f.ebner@proxmox.com> Tested-by: Wolfgang Bumiller <w.bumiller@proxmox.com> Reviewed-by: Wolfgang Bumiller <w.bumiller@proxmox.com> Link: https://lore.proxmox.com/20250404133204.239783-7-f.ebner@proxmox.com
This commit is contained in:
committed by
Thomas Lamprecht
parent
db5c50c079
commit
e2dc01ac9f
@ -42,11 +42,11 @@ use PVE::Storage::BTRFSPlugin;
|
||||
use PVE::Storage::ESXiPlugin;
|
||||
|
||||
# Storage API version. Increment it on changes in storage API interface.
|
||||
use constant APIVER => 10;
|
||||
use constant APIVER => 11;
|
||||
# Age is the number of versions we're backward compatible with.
|
||||
# This is like having 'current=APIVER' and age='APIAGE' in libtool,
|
||||
# see https://www.gnu.org/software/libtool/manual/html_node/Libtool-versioning.html
|
||||
use constant APIAGE => 1;
|
||||
use constant APIAGE => 2;
|
||||
|
||||
our $KNOWN_EXPORT_FORMATS = ['raw+size', 'tar+size', 'qcow2+size', 'vmdk+size', 'zfs', 'btrfs'];
|
||||
|
||||
|
||||
Reference in New Issue
Block a user