Adding Back Legacy Fields to Avoid Breaking Changes in DataMaskingRules.json#39317
Merged
ericshape merged 1 commit intoAzure:publish-sql-Microsoft.Sql-2025-02-01-previewfrom Dec 17, 2025
Conversation
skpadhy33
requested review from
achyuth-ms,
ericshape,
jamestao,
jeremyfrosti and
mitesh-pv
as code owners
microsoft-github-policy-service
bot
added
customer-reported
Next Steps to MergeImportant checks have failed. As of today they are not blocking this PR, but in near future they may.Addressing the following failures is highly recommended:
Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
mitesh-pv
approved these changes
Dec 17, 2025
github-actions
bot
added
brownfield
ericshape
approved these changes
Dec 17, 2025
ericshape
merged commit b67fceb
into
Azure:publish-sql-Microsoft.Sql-2025-02-01-preview
51 of 55 checks passed
jeremyfrosti
added a commit
that referenced
this pull request
Mar 4, 2026
* Create base of release-sql-Microsoft.Sql-2025-02-01-preview via Copy-ApiVersion.ps1 (#36370) * Copy files from preview/2024-11-01-preview Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec. * Update version to preview/2025-02-01-preview Updated the API version from preview/2024-11-01-preview to preview/2025-02-01-preview. * Added tag for 2025-02-01-preview in readme file --------- Co-authored-by: Mitesh Vishwakarma <mvishwakarma@microsoft.com> * Swagger changes for Paginated List DDM rules API (#36819) Co-authored-by: Santosh Padhy <santoshpadhy@microsoft.com> * Datasync UAMI support API in 2025-02-01-preview (#35876) * Datasync UAMI support API in 2025-02-01-preview * Updated json to fix validation failure * Spell, lint fix * Fix error message * Updating error codes --------- Co-authored-by: Hareesh Kumar Gajulapalli <hgajulapalli@microsoft.com> * Azure SQL API Parity (#38442) * Azure SQL API Parity * avocado error update * fixes lint diff errors --------- Co-authored-by: mvishwakarma <mvishwakarma@microsoft.com> * Removing datasync breaking change because of required fields (#39059) Co-authored-by: Hareesh Kumar Gajulapalli <hgajulapalli@microsoft.com> * Added back the legacy params (#39317) Co-authored-by: Santosh Padhy <santoshpadhy@microsoft.com> * 20250201-preview breaking change fix for databases.json (#40027) * breaking change fix * fix model validation failure --------- Co-authored-by: mvishwakarma <mvishwakarma@microsoft.com> * fixing model validation errors (#40364) * fixing model validation errors * adds model validation fix * fixes model validation errors * Fixes model validation errors * fixes model validation failures * model valdation fixes ' * model validation fix * model validation fixes * fixes model validation errors --------- Co-authored-by: mvishwakarma <mvishwakarma@microsoft.com> * fix semantic error * fix semantic error * add v2 * fix breaking change (#40593) Co-authored-by: mvishwakarma <mvishwakarma@microsoft.com> * Adding suppressions previously approved in #38470 (#40764) * Removing the list import export operation results from Servers API (#40836) * Adding suppressions previously approved in #38470 * Removing the list import export operation results from Servers API * Fix for lint-diff errors (#40792) * Fix for lint-diff errors * Rectifies suppression for ResourceNamePattern * Remove ResourceNameRestriction validation code Removed ResourceNameRestriction code from parameters. * Fix formatting issue Fix formatting issue --------- Co-authored-by: mvishwakarma <mvishwakarma@microsoft.com> Co-authored-by: Jeremy Frosti <111934615+jeremyfrosti@users.noreply.github.com> * Add suppression for ElasticPools to match existing suppression in Databases (#40862) * Adding suppressions previously approved in #38470 * Removing the list import export operation results from Servers API * Adding suppression for new currentSku in ElasticPool update --------- Co-authored-by: Mitesh Vishwakarma <mvishwakarma@microsoft.com> Co-authored-by: skpadhy33 <35034191+skpadhy33@users.noreply.github.com> Co-authored-by: Santosh Padhy <santoshpadhy@microsoft.com> Co-authored-by: hareeshghk <hareeshghk@users.noreply.github.com> Co-authored-by: Hareesh Kumar Gajulapalli <hgajulapalli@microsoft.com> Co-authored-by: zedy <zedy@wicresoft.com> Co-authored-by: Jeremy Frosti <111934615+jeremyfrosti@users.noreply.github.com>
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
4 participants
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.
Some legacy fields were removed from the response objects for the new (2025-02-01) version of the Data Masking Rules API as they had not been in use. This leads to breaking changes in the 2025-02-01 version of the API.
Original PR introducing the 2025-02-01 version of the Data Masking Rules API: #36819
In this PR, we are adding back those legacy fields to avoid the breaking changes. Although these fields would not be used, but still be retained to avoid breaking changes.