dsccommunity / dsccommunity/SqlServerDsc
SqlWindowsFirewall: For feature RS it should not create rules for both port 80 and 443 by default
Nobody has claimed this yet.
- 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:
Today when feature 'RS' is sent to xSQLServerFirewall it will open up both ports 80 and 443. The user should be able to decide which port or ports to open.
The DSC configuration that is using the resource (as detailed as possible):
xSQLServerFirewall FirewallConfiguration
{
Ensure = 'Present'
SourcePath = $Node.SourcePath
InstanceName = $Node.InstanceName
Features = 'RS'
PsDscRunAsCredential = $SqlInstallCredential
}
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Any
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
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
Start at the xSQLServerFirewall resource and trace how Features = 'RS' is translated into firewall rules. Review the resource's existing tests, if available, and confirm the completed behavior against the requirement that RS should not unconditionally create rules for both ports 80 and 443.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100