OCI and wildcard version

[dpiraud]

Hello,

One of my applications publish helm charts in an OCI registry with this kind of version (appname-incrementalIndex-commitHash-dev);

• my-api-3-xyz-dev
• my-api-2-ijk-dev
• my-api-1-abc-dev

And I use this kind of config for Argo CD:

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: xxxx
  namespace: xxxx
spec:
  syncPolicy:
    automated:
      selfHeal: true
  destination:
    name: ''
    namespace: xxx
    server: 'xxx'
  source:
    path: ''
    repoURL: registry.xxx/helm
    chart: my-api
    targetRevision: '>0.0.0-0'
  project: xxx

Let's say the current deployed app is from helm "api-2-ijk-dev"

I'm only able to install the latest version (api-3-xyz-dev) if i hit the "Refresh Hard" button, Argo CD won't do it automatically.

Is there a way to improve this?

P.S.: I also try with '>0.0.0-0-0-0' and all sorts of target version without success

EDIT:
ArgoCD v2.3.3

[rowi1de]

I also missed that there feature is there #9509 (reply in thread)

[fe-ax]

Since OCI doesn't seem to implement a search function. I think this feature cannot be implemented without it. Would it be a possibility to tag helm charts with partial versioning?

Version 3.6.3 tagged 3.6.3 3.6 3 latest

[rowi1de]

@dpiraud did you try to use correct SemVer semantics for patch / pre-release? Like 0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.–.
https://semver.org/#spec-item-9

Or build metadata? 1.0.0+20130313144700

A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUST comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes. Pre-release versions have a lower precedence than the associated normal version. A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.–.

Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or pre-release version. Identifiers MUST comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-]. Identifiers MUST NOT be empty. Build metadata MUST be ignored when determining version precedence. Thus two versions that differ only in the build metadata, have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85, 1.0.0+21AF26D3—-117B344092BD.

[dpiraud]

@rowi1de I'll have a look on my pre-release version format ang give feedback, thx!