CHORE: add OneBranch release pipeline scaffolding - #546
Merged
Conversation
Introduces the shared scaffolding for the mssql-django release pipelines (build / official-release / dummy-release), mirroring the in-repo layout used by microsoft/mssql-python. No pipeline definitions are wired yet; this lands only the variables and SDL/governance config they will consume. - OneBranchPipelines/variables/common-variables.yml: paths, package identity, pip feed, and the regex_clr.dll blob coordinates (fetched at build time via managed-identity auth, not committed to the repo). - OneBranchPipelines/variables/onebranch-variables.yml: OneBranch output directory, SDL/TSA toggles, Linux build image. - .config/tsaoptions.json, .config/CredScanSuppressions.json: SDL config. - es-metadata.yml: ES/OneBranch governance metadata. mssql-django is pure-Python, so no native/ODBC/symbol tooling is included. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Match the blessed mssql-python governance format (adapted for Django) rather than the legacy mssql-django-tools variants: - es-metadata.yml: InventoryAsCode schemaVersion 1.0.0 - .config/tsaoptions.json: python-shape with include/exclude path patterns - .config/CredScanSuppressions.json: python-shape suppressions - common-variables.yml: drop the subscription id from comments (no internal identifiers in a public repo) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
workspace_pr_body.md is a local PR-body draft, not part of the scaffold. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
📊 Code Coverage Report
Diff CoverageDiff: dev...HEAD, staged and unstaged changesNo lines with coverage information in this diff. 📋 Files Needing Attention📉 Files with overall lowest coverage (click to expand)- mssql/client.py: 19.5% (41 lines)
- mssql/__init__.py: 50.0% (2 lines)
- mssql/creation.py: 56.8% (74 lines)
- mssql/base.py: 68.3% (514 lines)
- mssql/operations.py: 78.8% (396 lines)
- mssql/compiler.py: 79.5% (640 lines)
- mssql/functions.py: 83.2% (428 lines)
- mssql/schema.py: 86.1% (719 lines)
- mssql/introspection.py: 90.7% (129 lines)
- mssql/features.py: 98.8% (83 lines)🔗 Quick Links
|
This was referenced Jul 27, 2026
bewithgaurav
marked this pull request as ready for review
July 27, 2026 07:16
Contributor
There was a problem hiding this comment.
Pull request overview
Adds foundational OneBranch/SDL governance and variable scaffolding needed to author mssql-django release pipelines (build package + official + dummy), without wiring actual pipeline definitions yet.
Changes:
- Introduces shared pipeline variable templates (package identity, artifact paths, OneBranch/SDL/TSA toggles, and regex_clr.dll blob coordinates).
- Adds SDL governance configuration files for TSA and CredScan suppressions.
- Adds ES/OneBranch governance metadata (
es-metadata.yml) for inventory/routing.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
OneBranchPipelines/variables/common-variables.yml |
Defines common release variables (repo/artifact paths, package identity, feed, regex_clr.dll storage coordinates). |
OneBranchPipelines/variables/onebranch-variables.yml |
Defines OneBranch-specific variables (artifact output directory, SDL/TSA toggles, Linux container image). |
.config/tsaoptions.json |
Adds TSA configuration (instance/project metadata + include/exclude path patterns). |
.config/CredScanSuppressions.json |
Adds CredScan suppression configuration intended to suppress known false positives/examples. |
es-metadata.yml |
Adds ES governance metadata for inventory/routing. |
jahnvi480
approved these changes
Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the shared scaffolding for the mssql-django release pipelines
(build-release-package / official-release / dummy-release), mirroring the
in-repo layout used by
microsoft/mssql-python. No pipeline definitions arewired yet — this PR only lands the variables and SDL/governance config the
pipelines will consume.
OneBranchPipelines/variables/common-variables.ymlregex_clr.dllblob coordinatesOneBranchPipelines/variables/onebranch-variables.yml.config/tsaoptions.json.config/CredScanSuppressions.jsonCONTRIBUTING.mdexample)es-metadata.ymlWhy
Part of moving mssql-django's release machinery out of the standalone
mssql-django-toolsADO repo and into the product repo (parity withmicrosoft/mssql-python), so build / release / sync all live and versionalongside the code.
Notes
regex_clr.dlldeliberately stays out of the repo (security policy) and isfetched at build time from the private storage account via managed-identity
auth — wired in the follow-up build-pipeline PR.