#variant - October 2020

@mumoshu see the new announcement today from HashiCorp on Waypoint?
https://www.waypointproject.io/

Example config:
https://github.com/hashicorp/waypoint-examples/blob/main/kubernetes/exec-kubectl-apply/waypoint.hcl

@Erik Osterman (Cloud Posse) Just read the announcement. Looks nice!

Probably variant could be handy when used from waypoint hooks(https://www.waypointproject.io/docs/lifecycle/hooks) and exec plugin(https://www.waypointproject.io/plugins/exec)

The most impressive aspect of it for me was https://www.waypointproject.io/docs/internals/execution#most-common-cli-and-a-remote-server

Apparently you can start from no server, and gradually move heavy processes to the waypoint server in the future

https://www.waypointproject.io/docs/roadmap#remote-runners

Turns out Waypoint is not make or variant at all. It's a pluggable PaaS powered by not cli only but also waypoint-entrypoint and waypoint-server

Probably we may use variant to wrap waypoint-cli or call variant commands via waypoint's exec plugin

I found Porter a project which was accepted by the CNCF recently.
I am still trying to understand whether it is close to what variant dose!

Package your application artifact, client tools, configuration and deployment logic together as a versioned bundle that you can distribute, and then install with a single command

variant is mostly a HCL-based DSL and the compiler to build CLI apps. So my guess is that porter should be used to package variant-made apps 🙂

also - it may theoretically possible to export your variant-made command as a porter bundle by using https://porter.sh/custom-dockerfile/.

You can now turn your Variant2 command into a Kubernetes controller
See https://github.com/mumoshu/variant2/pull/35