When cloud versioning is enabled, DVC will store files in the remote according to their original directory location and filenames. Different versions of a file will then be stored as separate versions of the corresponding object in cloud storage. This is useful for cases where users prefer to retain their original filenames and directory hierarchy in remote storage (instead of using DVC's usual content-addressable storage format).
Note that not all DVC functionality is supported when using cloud versioned remotes, and using cloud versioning comes with the tradeoff of losing certain benefits of content-addressable storage.
Cloud versioning features are only avaible for certain storage providers.
Currently, it is supported on the following
dvc remote types:
- Amazon S3 (requires S3 Versioning enabled buckets)
- Microsoft Azure Blob Storage (requires Blob versioning enabled storage accounts and containers)
- Google Cloud Storage (requires Object versioning enabled buckets)
Lifecycle management policies may delete object versions, in which case DVC will be unable to recover those versions. For more information about lifecycle management, see:
version_aware option is enabled on a
dvc pushwill utilize cloud versioning when storing data in the remote. Data will retain its original directory structure and filenames, and each version of a file tracked by DVC will be stored as a new version of the corresponding object in cloud storage.
dvc pullwill download the corresponding version of an object from cloud storage.
Note that when
version_aware is in use, DVC does not delete current versions
or restore noncurrent versions of objects in cloud storage. So the current
version of an object in cloud storage may not match the version of a file in
your DVC repository.