#variant - April 2019 | Slack Archive | Cloud Posse

#variant - April 2019

variantArchived

21 messages

Discuss variant (the “Universal CLI”) https://github.com/mumoshu/variant

Archive: https://archive.sweetops.com/variant/

April 2019

mumoshualmost 7 years ago

fixed in the latest release

mumoshualmost 7 years ago

@oscarsullivan_old good catch! something seems wrong with the version command. It should print v0.27.1 at least

mumoshualmost 7 years ago

How do I ensure the latest version of Variant is on my module?

there's no way currently. i was thinking that you'll prefer wrapping the whole variant command up into a docker image, so that you can tie a specific version of variant and your variant command

but that's not always the case?

mumoshualmost 7 years ago

i wonder if it helps to add variantVersion that is written in your variant command like:


variantVersion: 0.27.0

so that running ./yourcmd on a machine with an older or newer version of variant immediately fails

wdyt?

mumoshualmost 7 years ago

Are you saying every command that is run has a version output?

no

mumoshualmost 7 years ago

How would you get the latest version for idea 2 to compare against?

Not sure I'm following you correctly, but I'd fix variant to properly embed its own version(like 0.27.0). So that when your variant command gets loaded by the variant(as the runtime), variant can see what version of runtime is required by the command wants, and validate if its own version matches the required version

Erik Osterman (Cloud Posse)almost 7 years ago

@mumoshu you are correct that in our case we can just check what version of the apk is installed

Erik Osterman (Cloud Posse)almost 7 years ago(edited)

though if variant is installed natively without a package manager, there’s really no way to know what version is installed

Erik Osterman (Cloud Posse)almost 7 years ago

Something like https://stackoverflow.com/a/11355611/1237191

Erik Osterman (Cloud Posse)almost 7 years ago

yes, i have no good idea how we force embed the version number when it is installed natively with go get

Erik Osterman (Cloud Posse)almost 7 years ago

one thing I’ve seen (and considered implementing at cloudposse) is adding a sentinel file for the version that is committed in the repo

Erik Osterman (Cloud Posse)almost 7 years ago

that way even releases are peer reviewed

Erik Osterman (Cloud Posse)almost 7 years ago(edited)

and then have the CI system apply the release tag from the sentinel file on merge to master

Erik Osterman (Cloud Posse)almost 7 years ago

yea, there are some 3rd party tools that will do it

lorenalmost 7 years ago

there's also http://labix.org/gopkg.in

lorenalmost 7 years ago

but i think it only pins to major version, which was a major bummer when i looked at it last

mumoshualmost 7 years ago

thx for sharing 🙂

Alexander Tolstikovalmost 7 years ago

@mumoshu do you want a motto for variant?

“One glue to glue them all” 🙂

Alexander Tolstikovalmost 7 years ago(edited)

@mumoshu probably we can discuss it: https://github.com/mumoshu/variant/issues/73#issuecomment-484868234

mumoshualmost 7 years ago

@Alexander Tolstikov Thx for chiming in! Replied.

Alexander Tolstikovalmost 7 years ago

@mumoshu hey, please check: https://github.com/mumoshu/variant/pull/74

March 2019 Browse by date May 2019