Feature Request: Add semver support about vendir HOT 14 CLOSED

@ciriarte first pass for git ref selection is on develop. example: https://github.com/k14s/vendir/blob/develop/examples/versionselection/vendir.yml. give it a go and lmk.

from vendir.

+1 It will really helpful as we are also planning to consume other external components as libraries and this would help us to pin to a particular version.

from vendir.

i wonder if we should make this functionality more generic since vendir currently supports git and github release, but will also support sources such as docker images, helm charts, etc. ... or does it make sense to just keep it source specific?

from vendir.

+1 for this.

The syntax I have used for this in the past was something like this BTW [1.0.0, 2.0.0); i.e. get the latest available from 1.0.0 up to but excluding 2.0.0.

from vendir.

i wonder if we should make this functionality more generic since vendir currently supports git and github release, but will also support sources such as docker images, helm charts, etc. ... or does it make sense to just keep it source specific?

Yes. It shouldn't be specific to a source.

from vendir.

sources:

• git (via tags)
• githubRelease (via tags)
• helm chart (via versions)
• image (via tags)
• http (???)

from vendir.

The Pivnet resource (and various other Concourse-ecosystem resources) accomplish some of this with regex filters; this allows expressive constraints of what versions will be included/excluded without having to create/document/maintain yet-another version specification DSL, or adopt one of the various (sometimes pretty complex) existing ones.

This also allows a distinction between the "explicit string" version key and a mutually-exclusive version-regex string, if desired.

Why not allow, for example,
version-regex: ^v1\..*

This also allows the use of sub-groups when using tags, and wanting to both be able to designate the "version" part while also being able to select from among multiple potentially version-matching tags, such as release-v1.0.0 and candidate-v1.0.0, for example.

from vendir.

it seems to be pretty uncommon to use regex for version constraints compared to ">=1, <2" commonly found in various package managers.

from vendir.

I like https://github.com/Masterminds/semver because it tries to be compatible with other package managers (in version 3+). Also, they have a a cli to perform quick validations https://github.com/Masterminds/vert which is useful for scripts/pipeline composition.

e.g. I often end up mucking with git describe --tags but vert already supports the transformation/filtering:

$ vert -g ^1 $(git describe --tags)
1.0.1+32.fef45

from vendir.

currently using hashicorps' go-version library (https://github.com/k14s/vendir/blob/develop/docs/versions.md).

from vendir.

@ciriarte first pass for git ref selection is on develop. example: https://github.com/k14s/vendir/blob/develop/examples/versionselection/vendir.yml. give it a go and lmk.

This is awesome. Will do and report back!

from vendir.

included in https://github.com/k14s/vendir/releases/tag/v0.11.0

from vendir.

switched to blang/semver in cb32f5a. this allows more control over when prerelease versions are included or not. added examples: https://github.com/k14s/vendir/blob/develop/docs/versions.md#examples. change will be available in v0.12.0+

from vendir.

updates are in https://github.com/k14s/vendir/releases/tag/v0.12.0

from vendir.