dsccommunity / dsccommunity/SqlServerDsc
SqlWindowsFirewall: Doesn't support multiple instances for Integration services and Reporting services
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 385
- Forks
- 224
- PR merge metrics
- No merged PRs in 30d
Description
Sqlwindowsfirewall creates generic name for firewall rule, that doesn't include the instance name for Integration services application, Integration services Port, Reporting services ports 80 and 443.
When we create second instance it causes error on the firewall rule name.
eg: SQL server Integration services Application
Fix: SQL server Integration services Application Instancename
i will post the fix for this issue.
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 by locating the SqlWindowsFirewall resource and the firewall-rule name generation for Integration Services and Reporting Services ports 80 and 443. Reproduce creation with a second instance, then verify that each affected rule name includes the instance name and no naming error occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100