-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for default encryption scope & block encryption scope override for blob container APIs. #8595
Conversation
…rride for blob container APIs.
Azure Pipelines successfully started running 1 pipeline(s). |
5 similar comments
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-java - Release
|
azure-sdk-for-go - Release
|
azure-sdk-for-js - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-python - Release
- Breaking Change detected in SDK
|
Can one of the admins verify this patch? |
specification/storage/resource-manager/Microsoft.Storage/stable/2019-06-01/blob.json
Show resolved
Hide resolved
"type": "string", | ||
"description": "Default the container to use specified encryption scope for all writes." | ||
}, | ||
"denyEncryptionScopeOverride": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
denyEncryptionScopeOverride [](start = 9, length = 27)
Consider to to use enum or string instead of boolean in case you need other mode which may cause breaking change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was intentionally modeled as a boolean to match data plane headers following the same.
Invite ARM review since this PR add properties in the put request. |
Azure Pipelines successfully started running 1 pipeline(s). |
azure-cli-extensions - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -797,6 +800,14 @@ | |||
"definitions": { | |||
"ContainerProperties": { | |||
"properties": { | |||
"defaultEncryptionScope": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding new writable properties to a stable API is considered a breaking change. Could this instead be moved into a new API version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add these 2 new properties should no be breaking since:
- Old sdk still work, as the new properties are optional
- Old SDK won't change the properties added with new SDK
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
@tonykjose , the CI failed because the breaking change in the API. Could you please help provide justified information for this breaking change and why not add a new API version? |
@akning-ms could you please help force merge this PR since the breaking change is accepted to SDK? |
Actually, the rest API itself is not breaking (Just add 2 properties), but the SDK generated from the swagger will break. I don’t think this break should block the swagger PR merge. Origin: New: |
…rride for blob container APIs. (Azure#8595) * Add support for default encryption scope & block encryption scope override for blob container APIs. * Add examples. * Fix prettier issues. * Fix prettier errors. * Really fix prettier errors.
…rride for blob container APIs.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.