dsccommunity / dsccommunity/SqlServerDsc

SqlServerDsc: Production ready configurations for scenarios should be created

Open
#977 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
PowerShell
Stars
385
Forks
224
PR merge metrics
No merged PRs in 30d

Description

Details of the scenario you tried and the problem that is occurring:
The obsolete "complete" examples are gonna be removed as per PR #976. I suggest that new production ready configurations should be implemented as configurations using the templates from the repository DscConfigurations. Then they are able to be integration tested by the users themselves with an already finished framework for production ready configurations. The configurations should be able to be linked to that DscConfigurations repository, and can also be linked too here.

I see that this can be configurations that contributors have in a repository that they maintain themselves, and could be linked from here as long as it uses the DscConfigurations framework.

The DSC configuration that is using the resource (as detailed as possible):
n/a

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
n/a

What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
n/a

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review PR #976 and the templates in the linked DscConfigurations repository to understand the expected production-ready configuration structure. Define the scenarios to cover, implement configurations that use that framework, and link them from SqlServerDsc or the contributing repositories; completion means the obsolete examples can be removed and users can integration-test the new configurations.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.