#variant (2019-02)

This feature will reduce repetitions in your scripts https://github.com/mumoshu/variant/issues/53

that’s awesome!

also, like that you support a list under script

are those ultimately joined as one script or each run in their own shell?

https://github.com/mumoshu/variant/issues/52

this!!

I want.

basically we can create a variant library, then create a cli that imports various capabiltiies

for example, we can create a helm lib, and a helmfile lib and a kops lib and a terraform lib with useful tricks

e.g. for terraform, automating force-unlock

then in the final implementation, we can include the libs that we want into our cli. for example, one customer might not use kops, so we wouldn’t need to import that lib.

and this https://github.com/mumoshu/variant/issues/51!

so cool

@mumoshu I am trying to run an interactive SSH session inside of variant, should that work?

I love it!!!

mixins:
  chamber: &chamber
    source <(chamber exec kops -- sh -c 'export -p' 2>/dev/null)

Then anywhere I want chamber, I can just do this:

          bastion:
            description: "Connect to the bastion using ssh-agent forwarding"
            interactive: true
            script:
            - *chamber
            - |
              set -e
              eval $(ssh-agent -s)
              ssh-add - <<<${KOPS_SSH_PRIVATE_KEY}
              ssh -A admin@bastion.${KOPS_CLUSTER_NAME}
              eval $(ssh-agent -k) >/dev/null

this is shell scripting on steroids

I tried to change the default runner by adding

should that work?

(in the global scope)

my first advanced variant script:

https://github.com/cloudposse/geodesic/pull/378

@daveyu has joined the channel

@michal.matyjek has joined the channel

@mallen has joined the channel

@Erik Osterman (Cloud Posse) wdyt? https://github.com/mumoshu/variant/issues/56

Ahhh yes, ultimately this becomes an issue.

I would like to discuss some idea that @Igor Rodionov had today

I am afk, so will pick up later

btw: https://github.com/mumoshu/variant/issues/51 and https://github.com/mumoshu/variant/issues/52 has been resolved and included in variant v0.20.0 (haven’t done much testing yet. briefly verified to work with github sources though

Wrote up an another issue that fills one of big missing pieces(to me): https://github.com/mumoshu/variant/issues/57

@joshmyers has joined the channel

https://github.com/mumoshu/variant have any docs?

Liking it so far but having to dig through all the tests

Unfortunately the integration tests are the best documentation at this time. Fortunately there are a lot of examples there though!

any contribution to docs is welcomed! (well, i’ll write more later :)

FYI: Trigger your Variant tasks via GitHub Actions https://github.com/mumoshu/github-actions/tree/master/variant

this is exciting!

github actions still don’t work on public projects, right?

@dennybaa has joined the channel

@richwine has joined the channel

@platinumnj has joined the channel

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

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

@nutellinoit has joined the channel