Asset Versioning & Automatic Retention Rules
  • 24 Sep 2021
  • 1 Minute to read
  • Dark
    Light
  • PDF

Asset Versioning & Automatic Retention Rules

  • Dark
    Light
  • PDF

Starting in ProGet v6.0.0, asset directories support versioning.

Versioning Overview

When versioning is enabled for an asset directory, any time a file is overwritten or deleted, its previous content is retained. Note that only the content of old versions is stored, not any associated metadata. This allows you to revert an accidental change or delete, and to download an old version of a file.

Versioning is supported using any of ProGet's storage mechanisms (disk or cloud), and works by maintaining copies of files whenever they are overwritten or deleted in a special ._proget_file_history_ directory.

Limitations

Asset content is archived, not asset metadata. Previous versions of assets are not replicated.

Versioning Best Practices

Asset directory versioning is intended to help safeguard against accidental destructive changes; it is not intended as a replacement of a differencing/change tracking systems such as source/version control. When using it with very large files, the asset directory could consume disk space rapidly if the files are changed often.

As with any tool that stores previous versions, take care not to put sensitive information in assets.

Retention Rules for Asset Directories

Asset directories support retention rules just like package feeds in ProGet. The most common use case for asset retention rules is to:

  • delete old versions of assets (when versioning is enabled)
  • delete infrequently accessed files (for example, when an asset directory is used as an on-premise cache of offsite resources)

Read more about retention rules at Retention Rules.


Was this article helpful?