microsoft / microsoft/go-sqlcmd
Should ~/.sqlcmd/sqlconfig keep metadata on what the endpoint is
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
The metadata for an endpoint looks like this:
endpoints:
- endpoint:
address: localhost
port: 1433
name: endpoint - asset:
container:
id: aeedc3821812c45120300a467cd82c90e5c049b4610256dfffb6701c99665f01
image: mcr.microsoft.com/mssql/server:latest
To be able to generate the best connection strings (from sqlcmd config connection-strings) should the metadata hold details on what the endpoint actually is, is it mssql-server, or mssql-edge, or azure sql db, or azure sql MI, or postgres!
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 reviewing the ~/.sqlcmd/sqlconfig endpoint metadata and the sqlcmd config connection-strings command. Determine whether the stored metadata should identify endpoint types such as SQL Server, Azure SQL, or PostgreSQL, and document the decision and expected connection-string behavior as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100