microsoft / microsoft/go-sqlcmd
Add support for non-tcp and named connection in add-endpoint
Open
Nobody has claimed this yet.
enhancement
sqlcmd switch
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
Creating this issue to track the support for non-tcp and named connection instances when adding endpoint via sqlcmd config add-endpoint
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 by tracing the sqlcmd config add-endpoint command and its existing handling of TCP connections. Identify how named connections and non-TCP connection instances are represented, then inspect the related tests if present. Done means the command accepts and correctly preserves both requested connection types, with coverage for each case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100