From 6e1672f73c8bbda764a2ca66cb9ea0ef78842083 Mon Sep 17 00:00:00 2001 From: Hidde Beydals Date: Fri, 12 Feb 2021 16:47:16 +0100 Subject: [PATCH] Change policy example to numerical in asc order Signed-off-by: Hidde Beydals --- docs/guides/flux-v1-automation-migration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/flux-v1-automation-migration.md b/docs/guides/flux-v1-automation-migration.md index f75af74b..b9e53da3 100644 --- a/docs/guides/flux-v1-automation-migration.md +++ b/docs/guides/flux-v1-automation-migration.md @@ -537,14 +537,14 @@ spec: pattern: '^main-[a-f0-9]+-(?P[0-9]+)' extract: '$ts' policy: - alphabetical: + numerical: order: asc ``` The `.spec.pattern` field gives a regular expression that a tag must match to be included. The `.spec.extract` field gives a replacement pattern that can refer back to capture groups in the filter pattern. The extracted values are sorted to find the selected image tag. In this case, the -timestamp part of the tag will be extracted and sorted alphabetically in ascending order. See [the +timestamp part of the tag will be extracted and sorted numerically in ascending order. See [the reference docs][imagepolicy-ref] for more examples. Once you have made sure you have image tags and an `ImagePolicy` that works, jump ahead to [Checking