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

[WIP] Microsoft.PowerShell.DSC module #507

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

Gijsreyn
Copy link

PR Summary

As mentioned in the previous PR at: #498, the name might be too ambitious, but I thought to give it a shot.

The goal of the module is to help PowerShell users write DSC V3 configuration documents and resources in a PowerShell-ish way. This helps users adopt DSC V3 concepts by relating known commands on the shell to DSCV1/V2 concepts.

Features to include:

  • Argument completers for PSDSC DSC resources. It should be able to output PowerShell objects that in the end are sent through the pipeline to dsc.exe as JSON.
  • Provide easy-to-use examples from the get-go.
  • Able to execute both .json, .yaml, or .ps1 files.
  • Leverage functionality from adapters e.g. PowerShell/WindowsPowerShell
  • ...

From this perspective in PS module format, it should be able to be checked for multiple PowerShell versions thanks to @gaelcolas and other contributors to the Sampler project. It can also be published easily in PowerShellGallery.

@Gijsreyn
Copy link
Author

@SteveL-MSFT Sorry was messing around with the branches, that's why I opened a new PR. Can you close #498?

@michaeltlombardi Can you skip the PR review on the previous one and when you have time, check this one out, please?

@SteveL-MSFT
Copy link
Member

@Gijsreyn I appreciate your efforts and enthusiasm on this. However, before you spend more time writing code, I think it would be best if we started a bit slower and agree on the goals and requirements, then the design, and then the code should follow. Note that prototype code for the purpose of evaluating feasibility and usability makes sense with the expectation that prototypes don't get turned into production code and prototype code is only intended for learning.

So perhaps we need to take a step back and just have a discussion starting with the intended goals of this project?

@Gijsreyn
Copy link
Author

Gijsreyn commented Aug 1, 2024

@SteveL-MSFT I agree. My enthusiasm took over too hard as my idea train was spinning through me. I forgot to align more on the goals and requirements and only took my own learnings into the idea when starting in the DSC V3 era. What you said about prototype code, I totally get it. As I'm quite new to the community, would it be great to pitch such prototype code at the PowerShell / PowerShell DSC community calls to gather traction and get more ideas flowing?

I'll take a step back for now and love to have further discussions on it. Best to do it here or on the discussions tab of this project? To keep things straightforward, feel free to point out any mismatches in vision or ideas in this project context if the module does not fit.

Thanks again for the quick response Steve.

@SteveL-MSFT
Copy link
Member

@Gijsreyn it would be great if you want to use the next Community Call to give a short demo of your prototype and point them to a discussion to solicit more feedback/ideas

@Gijsreyn
Copy link
Author

Gijsreyn commented Aug 2, 2024

Cool Steve, I will try to prepare a small demo for the community call on the 15th. I cannot attend the 21st of August because I will be going on holiday. Do I have to get in touch with Steven or Sydney?

@SteveL-MSFT
Copy link
Member

@Gijsreyn just add yourself to the agenda here: PowerShell/PowerShell#24123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants