dsccommunity / dsccommunity/SqlServerDsc
SqlFailoverClusterNode: New resource proposal
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 385
- Forks
- 224
- PR merge metrics
- No merged PRs in 30d
Description
Resource proposal
A class-based SqlFailoverClusterNode resource would manage adding or removing nodes in a SQL Server FCI, and completing cluster configuration steps. It would use Add-SqlDscNode, Remove-SqlDscNode, and Complete-SqlDscFailoverCluster.
Proposed properties
| Property | Type qualifier | Data type | Description | Default value | Allowed values |
|---|---|---|---|---|---|
| Ensure | Key | String | Whether the node should be Present or Absent in the FCI | Present | Present, Absent |
| NodeName | Key | String | Name of the cluster node | None | Any valid node name |
| InstanceName | Key | String | The SQL Server instance name | None | Any valid instance name |
| ClusterGroup | Write | String | Cluster group name | None | Any valid group name |
| ClusterIPAddress | Write | String[] | IP addresses for the cluster | None | Any valid IP address list |
Special considerations or limitations
Should ensure changes do not disrupt cluster availability, support coordination with setup and cluster resources, and handle permission and network requirements for cluster operations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation file or test is identified in the proposal. Start by examining the three named commands—Add-SqlDscNode, Remove-SqlDscNode, and Complete-SqlDscFailoverCluster—and existing resource patterns, then define completion around the listed properties and safe Present/Absent node management for a SQL Server FCI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, sql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100