Icinga / Icinga/icinga-powershell-framework
Allow local DB connections
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 87
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
With Integrated Security = True, currently there is no possibility to pass into Open-IcingaMSSQLConnection a local server connection (like server=(localdb)\myInstance, as described here ).
The port separated with a comma will always be there:
https://github.com/Icinga/icinga-powershell-framework/blob/262f0c432f61882aeb270ca45949de715afe0738/lib/mssql/Open-IcingaMSSQLConnection.psm1#L69C55-L69C67
Maybe there are some workarounds meanwhile? Trying to use Invoke-IcingaCheckMSSQLHealth for a Server\Instance...
Thank you
Contributor guide
No contributing guide indexed for this repository
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 with lib/mssql/Open-IcingaMSSQLConnection.psm1 at the linked connection-string construction, and compare its current port handling with the SQL Server connection-string documentation. Reproduce the issue through Invoke-IcingaCheckMSSQLHealth using a Server\Instance or localdb connection; done means a local server connection works with Integrated Security without requiring a port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100