Skip to content
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 setter to configure ClientOptions on processor builder #18148

Merged
merged 5 commits into from
Jan 14, 2021

Conversation

srnagar
Copy link
Member

@srnagar srnagar commented Dec 15, 2020

This PR adds a new setter method on the EventProcessorClientBuilder to configure ClientOptions.

Fixes #17595

Copy link
Member

@JonathanGiles JonathanGiles left a comment

Choose a reason for hiding this comment

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

Where did we end with ClientOptions? This will be the protocol-agnostic API and in the future we might introduce HttpClientOptions? Does applicationId and headers both make sense as being settable here?

@srnagar
Copy link
Member Author

srnagar commented Jan 7, 2021

@JonathanGiles ClientOptions are protocol agnostic. HttpClientOptions will extend from ClientOptions which will have HTTP-specific options. For AMQP, both application and headers are valid. So, adding this API makes sense for the processor client. Also, this API was already added to the EventHubClientBuilder. This PR is just adding the same API to EventProcessorClientBuilder.

@JonathanGiles
Copy link
Member

Yep - as discussed, just be sure to note that the headers are applicable to the admin client rather than the amqp clients.

Copy link
Contributor

@YijunXieMS YijunXieMS left a comment

Choose a reason for hiding this comment

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

LGTM

@srnagar srnagar merged commit 02c9dec into Azure:master Jan 14, 2021
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-java that referenced this pull request Apr 18, 2022
[Hub Generated] Public private branch 'elastic-san-preview' (Azure#18148)

* Initial Check-In to introduce ElasticSan RP

* Applied coding styles and fixed the spelling mistake.

* Updated with IOPS & MBps properties

* Updated swagger file with NetWork Acls

* Added "None" to protocol type and updated with other validations.

* Removed ElasticSan from VolumeGroup operations

* Addressed review comments by adding elasticSanName in each of its operation

* Added volumeGroupName Parameters to the operations

* Upated array item with "x-ms-identifiers": [] as per Swagger Lint recommendations

* Removed unused parameters

* Updated with Snapshot endpoints

* Updated with missing "type" declarations

* Added Snapshot changes and addressed the PR review comments

* Fixed Lint differences

* Fixed Lint difference

* Added Export feature for Snapshot

* Updated with Sku level settings

* Updated with AdditionalInfo with "x-ms-identifiers": []

* Fixed Lint compilation issue with "x-ms-identifiers": [],

* Fixed Prettier issues

* Updated the readme* files with the right package and namespaces.

* Pointed GO to track2

* Updated readme.go.md with the yaml format

* Addressed review comments, updated with ecommon types and added naming restrictions.

* Updated with common SystemData

* Corrected the missing json structure

* Updated 'CreateOrUpdate" with "Create"

* Updated the spec with Network ACLs

* Removed unnecessary error codes

* Regenerated the examples

* Removed Snapshot API and addressed PR comments (Azure#18638)

* Removed Snapshot API and addressed PR comments

* Removed Ruby SDK information (Azure#18662)

* Reverted tsconfig.json and removed Ruby related SDK information.

* Corrected the indentation for swagger-to-sdk

Co-authored-by: Rajesh Kumar Aggani <raaggani@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Expose clientOptions in EventProcessorClientBuilder
4 participants