liveBook · Manning

Versioning

As explained in Microsoft Azure in Action

Source control is a system for recording, comparing, and managing versions of files and their changes.

Versioning keeps earlier versions of blobs available when files are modified or deleted. Blob Storage creates and maintains a new version automatically, so an accidental change need not be the last word. section 9.3.1

For a storage account, the basic workflow is:

  • Enable versioning on the account; this turns it on for all its blob containers. section 9.3.1
  • List a blob’s versions to see details such as version ID, creation time, and content length. section 9.3.1
C:/> az storage account blob-service-properties update 
--account-name banningstorage --resource-group BanningRG 
--enable-versioning true

Enable versioning for the storage account with Azure CLI. section 9.3.1

C:/> az storage blob version list --account-name banningstorage 
--container-name <ContainerName> --name <BlobName> --output table

List versions for a named blob and container with Azure CLI. section 9.3.1

How Microsoft Azure in Action covers it

How deep it goes
Explains automatic version creation and recovery, then demonstrates enabling versioning and listing versions with CLI commands.
Examples
Uses a blob container of banned books and Azure CLI commands to enable versioning and list blob versions.
What it assumes
Assumes an Azure Storage account and blob container, and teaches versioning configuration through CLI commands.
What you can do after
Operate Azure CLI to enable blob versioning and inspect historical versions for recovery.
How it connects
Connects versioning to object replication, change feed, and lifecycle management.

Also explained in

Compare how 25 books explain versioning →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microsoft Azure in Action. The section links point to the parts of the book it draws on.