list_blob_versions | R Documentation |
List and delete blob versions
list_blob_versions(container, blob) delete_blob_version(container, blob, version, confirm = TRUE)
container |
A blob container. |
blob |
The path/name of a blob. |
version |
For |
confirm |
Whether to ask for confirmation on deleting a blob version. |
A version captures the state of a blob at a given point in time. Each version is identified with a version ID. When blob versioning is enabled for a storage account, Azure Storage automatically creates a new version with a unique ID when a blob is first created and each time that the blob is subsequently modified.
A version ID can identify the current version or a previous version. A blob can have only one current version at a time.
When you create a new blob, a single version exists, and that version is the current version. When you modify an existing blob, the current version becomes a previous version. A new version is created to capture the updated state, and that new version is the current version. When you delete a blob, the current version of the blob becomes a previous version, and there is no longer a current version. Any previous versions of the blob persist.
Versions are different to snapshots:
A new snapshot has to be explicitly created via create_blob_snapshot
. A new blob version is automatically created whenever the base blob is modified (and hence there is no create_blob_version
function).
Deleting the base blob will also delete all snapshots for that blob, while blob versions will be retained (but will typically be inaccessible).
Snapshots are only available for storage accounts with hierarchical namespaces disabled, while versioning can be used with any storage account.
For list_blob_versions
, a vector of datetime strings which are the IDs of each version.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.