microsoft / microsoft/go-sqlcmd
Use Microsoft Go tools for official builds
Open
Nobody has claimed this yet.
Security
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
Per guidance for Microsoft products, we need to build sqlcmd using the Microsoft build of Go toolset.
It's a prerequisite for enabling FIPs compliant builds before we can pick up the crypto code from go-mssqldb when we add Always Encrypted.
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
No files, tests, or entry points are named. Start by locating the official build configuration and current Go toolchain setup, then verify that the Microsoft Go toolset is used for sqlcmd builds and that the result supports the stated FIPS prerequisite before Always Encrypted work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100