#Dagger Interface for PowerShell

1 messages · Page 1 of 1 (latest)

autumn shuttle
sour turret
#

I've seen interest in a PowerShell API. I'd love to hear thoughts from other PS users about the shape of that API.

formal apex
#

Oh! I lived and breathed powershell for 4-5 years so this has me intrigued. Prefer Go now but I’ll have to check this out!

formal apex
#

Cool demo! Reminded me of DSC style language. Got me thinking of an InvokeBuild template invoking Dagger.

#

To be clear though with this target audience they are typically using Visual Studio not Visual Studio code. It’s different as much of the as actions are ui driven. Unlike in Go where almost everything is invoked via cli unless you go through the effort of building VSCode tasks in VS the terminal isn’t most likely the default go to. If there were Dagger build and run configurations maybe that would help later on though. That’s just my quick thoughts.

sour turret
#

F5 is probably the most common for local builds, but they still need build-test scripts for CI. We have a build.ps1 in each repo.