Open johlju opened 3 years ago
Project Site: https://github.com/MethodsAndPractices/vsteam PowerShell Gallery: https://www.powershellgallery.com/packages/VSTeam
Project Site: https://github.com/StartAutomating/PSDevOps PowerShell Gallery: https://www.powershellgallery.com/packages/PSDevOps
Hi @johlju are you still on it? I am a maintainer of the VSTeam module. Seems like to activity since the beginning of the year.
I might help you to get some light into what VSTeam supports. Which is actually a lot I think. It is mainly wrapping API 1:1 and additional having some higher abstracted cmdlets.
On order to have a DSC module working properly and easy to extend. This might help.
@SebastianSchuetze - I am the core maintainer and unfortunately due to other more pressing matters last year (I do volunteer vaccinating) & also moving house this project has been a little left to the side. However I am picking this back up from today as I will be presenting at PSConfEU in Vienna this June on this module and the full process in building it for the gallery.
I have used VSTeam in the past and followed it since it was very early days in development & was one of my main reasons for looking to use it as a base module in this DSC Resource Module is that it has a good surface area to the API's for what we would need for resources in this module. Give me this weekend coming to get my project plan for the upcoming months in place and I'll reach out to you to chat more (I've Just followed you on Twitter btw)
Cool. Hit me with info as soon as you are ready.
Any update how to proceed?
We should investigate if it possible to use either the module VSTeam or PSDevOps instead of inventing the wheel again. If we choose to do so, then we should make sure PR's does not add functionality that should be contributed to the module we choose.
From @kilasuit in PR #7:
A dependent module could be added in a similar way as the module
DscResource.Common
is used.