Skip to content
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

AzureDevsOpsDsc: Make use of either PowerShell module VSTeam or PSDevOps #27

Open
johlju opened this issue Jan 27, 2021 · 5 comments
Open
Assignees
Labels
Backlog - Short Term Backlog - Short Term needs investigation The issue needs to be investigated by the maintainers or/and the community.

Comments

@johlju
Copy link
Member

johlju commented Jan 27, 2021

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:

I had initially intended to make use of either VSTeam or PSDevOps as the base module for this and essentially build wrappers around either of them. However lets keep on track with what you've built so far here & discuss down the line about whether or not we go down differing path.

A dependent module could be added in a similar way as the module DscResource.Common is used.

@johlju johlju changed the title AzureDevsOpsDsc: Make Use either PowerShell module VSTeam or PSDevOps AzureDevsOpsDsc: Make use of either PowerShell module VSTeam or PSDevOps Jan 27, 2021
@johlju
Copy link
Member Author

johlju commented Jan 27, 2021

@johlju johlju added the needs investigation The issue needs to be investigated by the maintainers or/and the community. label Jan 27, 2021
@SebastianSchuetze
Copy link

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.

@kilasuit
Copy link
Contributor

kilasuit commented Jan 7, 2022

@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)

@kilasuit kilasuit self-assigned this Jan 7, 2022
@SebastianSchuetze
Copy link

Cool. Hit me with info as soon as you are ready.

@kilasuit kilasuit added Backlog - Short Term Backlog - Short Term Backlog - Mid Term Backlog - Mid Term and removed Backlog - Mid Term Backlog - Mid Term labels Jan 12, 2022
@SebastianSchuetze
Copy link

Any update how to proceed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog - Short Term Backlog - Short Term needs investigation The issue needs to be investigated by the maintainers or/and the community.
Projects
None yet
Development

No branches or pull requests

3 participants