Tag Tracking with Wildcard and Semantic Versioing doesnt work as expected

[Spazzy757]

We have a case where we use different suffixes to designate different environments i.e

• v*.*.*-stag
• v*.*.*-prod

According to SemVar this suffix falls into the "Additional Metadata" category.

However with ArgoCD when we designate a targetRevision: "v*.*.*-stag" It seems to pick up ALL tags with v*.*.* and completely ignores the suffix.

According to the docs it says:

For Git, all versions are Git references but tags Semantic Versions can also be used

Should the above scenario work, or am I misunderstanding the wildcard implementation

[holgerson97]

Is there any revision without the suffix in the repository?

[holgerson97]

I think "v" Prefix is not supported, as stated in SemVer:

SemVer

Is “v1.2.3” a semantic version?
No, “v1.2.3” is not a semantic version. However, prefixing a semantic version with a “v” is a common way (in English) to indicate it is a version number. Abbreviating “version” as “v” is often seen with version control. Example: git tag v1.2.3 -m "Release version 1.2.3", in which case “v1.2.3” is a tag name and the semantic version is “1.2.3”.

[Spazzy757]

We get the same result without the v as we do with it, it just picks up the latest tag, regardless of if it matches fully

[holgerson97]

So you also tried with tags without Prefix v?

[Spazzy757]

Yup, and changed the targetRevision to be: *.*.*-stag

[Spazzy757]

also tried 0.*.*-stag but prod still picks it up as well with 0.*.*-prod

[jose-arcatar]

I got the same problem, hopefully this get added in a future release

[Spazzy757]

Seems there is an open issue about this: #18899

[Spazzy757]

I created a PR: that should fix this: #20862