Paul Hatcher

So a consequence of wanting to purge images from your container registry is sometimes you need to keep some of them.

One example is that in regulated industries you must be able to produce software that was deployed to production for audit/legal purposes, so if you are purging images that are over 3 months old you might have an issue.

You can update an image so that it can’t be overridden or deleted via the az acr repository update command e.g.

One housekeeping task if you are producing docker images is clearing your container registry of old images.

I’ve been particularly bad at this and had also made some mistakes such as publishing PR images and images produced via our auto-patching runs, leading to the ACR size being >1.2Tb (ouch!).

There are some features introduced by acr auto purge, but I found an issue since my images typically have three tags…

1. Build number produced by Azure DevOps, needed as release pipelines can’t pass the version
2. The git SHA1, easy tracing back to the source code rather than just the build
3. Version number produced by gitversion (also on the source as a tag)

When I tried to remove an image via a tag, it removed the tag but not the manifest due to the other tags referencing it. The documentation says that this should work, but it doesn’t appear to.

I have a draft updated WikiExport to NET 6/8 since NET 3.1 is EOL

This release also has a couple of bug fixes

• Missing images causes export to fail
• Image paths not correct if no caption

Have it as a beta release at the moment until a bit more operational testing has been done.

Just pushed a new version of WikiExport with a couple of useful features

• Change titleFormat to have explicit {project}/{title} macros
• Support for .attachments in non-root folder - provided by @ricfre

The first is just a simplification since it’s more intentional to use named values rather than {0} etc, and we can also automatically determine projectInTitle from the titleFormat.

The second one allows support for code wikis and the image path not being in the root of the repository e.g. the repository may look a bit like this…