James

@keur Awesome-- one disclosure: this is a hard problem (you've been warned) and it's not 100% clear what's blocking us. Last I looked, this might be helpful... https://github.com/purpleidea/mgmt/blob/f342e06ef0d0fc173dcb5320e9a376f14d561868/lang/interpret_test.go#L324 https://github.com/purpleidea/mgmt/blob/f342e06ef0d0fc173dcb5320e9a376f14d561868/lang/lang_test.go#L884 I...

After some more digging, this is very _low_ priority, since it's only needed for tests at the moment. Some notes: 1) We can't choose any algorithm that could fail even...

@aequitas Yeah, the name of the command is flexible, and if it's a flag or a subcommand :)

@aequitas Maybe it should even be a pre-step of running deploy?

@S-ign Okay-- to continue this learning experience, here are some lessons: 1) When submitting a patch (to most projects in general) it's considered OK for the maintainer to ignore it...

@S-ign Okay, we had a fun git hackthon today, and all looks good test wise =D It looks like you've added some extra functions and things in here. The bad...

/cc @margamanterola

We're in the home stretch to MVP, and would like to know what we're missing to satisfy our future users. Helps us know which patches to write first by understanding...

I approve =D

PS: This patch can get merged as soon https://github.com/purpleidea/mgmt/issues/334 is fixed, which should be any moment now. Don't let this block you, and make sure you're on golang 1.9+ for...