Service Bus : New Property deadLetteringOnFilterEvaluationExceptions added and AvroDeflate removed#2267
Conversation
| "description": "Enumerates the possible values for the encoding format of capture description.", | ||
| "enum": [ | ||
| "Avro", | ||
| "AvroDeflate" |
There was a problem hiding this comment.
Deleting an enum value is a Binary Breaking Change in SDKs; this is typically not permitted.
If this value is only used in a model schema that is returned from the service, I recommend that you leave it in the enum, and make a remark about it in the readme.md file indicating that the value is deprecated and not returned from the service.
Removing the enum value at this point is not recommended.
| "type": "string", | ||
| "description": "ISO 8061 Default message timespan to live value. This is the duration after which the message expires, starting from when the message is sent to Service Bus. This is the default value used when TimeToLive is not set on a message itself." | ||
| }, | ||
| "deadLetteringOnFilterEvaluationExceptions": { |
There was a problem hiding this comment.
Adding a property on an existing model -- ( //cc @ravbhatnagar )
Looks ok to me.
fearthecowboy
left a comment
There was a problem hiding this comment.
FYI: You have a couple of failures in the semantic validator - https://travis-ci.org/Azure/azure-rest-api-specs/jobs/329350277
I'd rather not remove the existing enum value; this will cause binary breaking changes in the generated SDKs.
Recommended to leave the value in, and make a note of it in the readme.md file
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
…i-specs into currentSB # Conflicts: # specification/servicebus/resource-manager/Microsoft.ServiceBus/stable/2017-04-01/servicebus.json
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
@v-Ajnava I'm ok with this; are you ready to have this merged? |
|
@fearthecowboy , yes you can merge. Thanks ! |
|
Was unable to find SDK Azure/azure-sdk-for-python PR for this closed PR. |
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
Changes in this PR
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger