-
Notifications
You must be signed in to change notification settings - Fork 868
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[enhancement]: Extensions with Powershell Core execution handler #4386
Comments
Hi @ckrueger1979, thanks for reporting! We are working on more prioritized issues at the moment but will get back to this one soon. |
@ckrueger1979 thanks for the suggestion. We are considering various options for new execution handlers, and this is one of them. |
@geekzter browsing through the code, it doesn't look hard to add this feature on the agent. Should be like 2 files to implement, possibly a bit more if we were to add proper linux support. On top of that the VstsTaskSdk would need to be ported. Most of the tasklib would be simple, the bits that do Authentication and load the object model would be more work. What are the reasons for not adding it? Last time I asked, years ago, it was to not have to add to the maintenance burden. But looking at the code the PowerShell and PowerShell3 handler have been stable and haven't had any major work done on them since forever. The VstsTaskSdk has been very stable as well. |
@geekzter @kirill-ivlev is there any update on this? I think that this is a much needed feature. |
This issue has had no activity in 180 days. Please comment if it is not actually stale |
Still hoping |
I'm also hoping too @jessehouwing. between typescript and powershellcore, i'd much rather use powershellcore. it's easier to write and debug. |
Still looking forward to get this feature. |
Describe your feature request here
Hi,
it would be great if a powershell core (pwsh) execution handler for extensions would be available.
If you have currently a powershell extension it's not easy to make it platform independant because you have to rewrite the extension completly in Typescript. Going from powershell 5 to powershell core is relativly easy.
Maintenance on Typescript extensions is much higher. There is a huge dependancy tree that has to be updated for security reasons regularly and there are much more breaking changes in the Node world then in the Powershell world.
greetings
Carsten
The text was updated successfully, but these errors were encountered: