Skip to content

Service Bus : New Property deadLetteringOnFilterEvaluationExceptions added and AvroDeflate removed#2267

Merged
fearthecowboy merged 7 commits intoAzure:masterfrom
v-Ajnava:currentSB
Jan 22, 2018
Merged

Service Bus : New Property deadLetteringOnFilterEvaluationExceptions added and AvroDeflate removed#2267
fearthecowboy merged 7 commits intoAzure:masterfrom
v-Ajnava:currentSB

Conversation

@v-Ajnava
Copy link
Contributor

@v-Ajnava v-Ajnava commented Jan 16, 2018

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

  • Added 'deadLetteringOnFilterEvaluationExceptions' for subscriptions and updated examples
  • Removed 'AvroDeflate' from CaptureDescription - encoding

PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

"description": "Enumerates the possible values for the encoding format of capture description.",
"enum": [
"Avro",
"AvroDeflate"
Copy link
Contributor

@fearthecowboy fearthecowboy Jan 16, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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": {
Copy link
Contributor

@fearthecowboy fearthecowboy Jan 16, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding a property on an existing model -- ( //cc @ravbhatnagar )

Looks ok to me.

Copy link
Contributor

@fearthecowboy fearthecowboy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@marstr marstr changed the base branch from current to master January 16, 2018 20:59
@azuresdkciprbot
Copy link

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: specification/servicebus/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

Ajit Maruti Navasare (MINDTREE LIMITED) added 2 commits January 17, 2018 15:17
…i-specs into currentSB

# Conflicts:
#	specification/servicebus/resource-manager/Microsoft.ServiceBus/stable/2017-04-01/servicebus.json
@azuresdkciprbot
Copy link

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: specification/servicebus/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

Copy link
Contributor

@fearthecowboy fearthecowboy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@fearthecowboy fearthecowboy added the Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates label Jan 22, 2018
@fearthecowboy
Copy link
Contributor

@v-Ajnava I'm ok with this; are you ready to have this merged?

@v-Ajnava
Copy link
Contributor Author

@fearthecowboy , yes you can merge. Thanks !

@fearthecowboy fearthecowboy merged commit 5942709 into Azure:master Jan 22, 2018
@AutorestCI
Copy link

Was unable to find SDK Azure/azure-sdk-for-python PR for this closed PR.

@AutorestCI
Copy link

@AutorestCI
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants