Question: adding InvokeBuild dependency?

[sundmoon]

I am new to Labilty, and still have some troubles with initial useful setup.
(These troubles are lightest among other 'lab bootstrapping' tools, but still there are present)

I'd like to make use of this excellent engine:
https://github.com/nightroman/Invoke-Build

But I'd like to taskify the internals of Start-LabConfiguration too.
What do you think about it?

[iainbrighton]

Hi @sundmoon - glad to have you here 😉.

I'm happy to take suggestions about how you think we can make things better/easier. If that involves Invoke-Build or PSake it doesn't matter to me; too much. If you list out your thoughts here and we can then get the discussion going!

Thanks, Iain

[sundmoon]

Thank you @iainbrighton
Please consider this
https://gist.github.com/sundmoon/c7cdb92954447b7c69c54ee83610cb42

[sundmoon]

I'd suggest publishing some internals of src/Private

[iainbrighton]

@sundmoon This looks interesting! I have no problem with this as long as Invoke-Build doesn't become a dependency - unless you want to use it to jump-start the deployment. Are you envisioning adding an Invoke-Build file for each individual example?

[sundmoon]

@iainbrighton Sorry for my delay.
I am Ok with adding Invoke-Build per example.

But I am still sure that Start-LabConfiguration cmdlet got overdone of monolithication and a bit of "reverse engeneering" is needed there, preferably from its author.
I'm volunteering to make extensive testing of the stuff if you decide to decompose it.