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

Enable properties which supported in sdk #22676

Merged

Conversation

zhichengliu12581
Copy link
Contributor

@zhichengliu12581 zhichengliu12581 commented Jun 30, 2021

enable properties which supported in sdk
related pr

@ghost ghost added the azure-spring All azure-spring related issues label Jun 30, 2021
@check-enforcer
Copy link

check-enforcer bot commented Jul 2, 2021

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci

@stliu
Copy link
Member

stliu commented Jul 14, 2021

docs?

@zhichengliu12581
Copy link
Contributor Author

zhichengliu12581 commented Jul 14, 2021

@stliu I'm waiting for the review for this pr, which have conflict with this pr. I plan to modify the document and changelog after that pr merge. Or I can add it temporarily, and then modify it again after that pr merge?

@zhichengliu12581 zhichengliu12581 marked this pull request as ready for review July 23, 2021 02:35
@@ -16,6 +18,8 @@

private String connectionString;

private AmqpRetryOptions retryOptions = new AmqpRetryOptions().setTryTimeout(ServiceBusConstants.OPERATION_TIMEOUT);
Copy link
Member

Choose a reason for hiding this comment

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

Is this default value for servicebus sdk client? If so, seems we don't set it here

- Support configuration of `serviceBusReceiveMode` for ServiceBusClientConfig with property of `spring.cloud.stream.servicebus.<queue or topic>.bindings.<channelName>.consumer.serviceBusReceiveMode`, supported values are `PEEK_LOCK` and `RECEIVE_AND_DELETE`.
- Support configuration of `enableAutoComplete` for ServiceBusClientConfig with property of `spring.cloud.stream.servicebus.queue.bindings.<channelName>.consumer.enableAutoComplete`.
### Breaking Changes
- Deprecated the `spring.cloud.stream.servicebus.queue.bindings.<channelName>.consumer.concurrency` property,
Copy link
Contributor

Choose a reason for hiding this comment

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

Deprecated --> Deprecate

@@ -63,6 +63,8 @@ public ServiceBusQueueClientFactory queueClientFactory(
Assert.notNull(connectionString, "Service Bus connection string must not be null");

DefaultServiceBusQueueClientFactory clientFactory = new DefaultServiceBusQueueClientFactory(connectionString, properties.getTransportType());
clientFactory.retryOptions(properties.getRetryOptions());

Copy link
Contributor

Choose a reason for hiding this comment

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

can we delete the empty line here?

@@ -72,6 +72,8 @@ public ServiceBusTopicClientFactory topicClientFactory(
Assert.notNull(connectionString, "Service Bus connection string must not be null");

DefaultServiceBusTopicClientFactory clientFactory = new DefaultServiceBusTopicClientFactory(connectionString, properties.getTransportType());
clientFactory.retryOptions(properties.getRetryOptions());

Copy link
Contributor

Choose a reason for hiding this comment

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

can we delete the empty line here?

@yiliuTo
Copy link
Member

yiliuTo commented Jul 30, 2021

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@yiliuTo
Copy link
Member

yiliuTo commented Jul 30, 2021

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@yiliuTo yiliuTo self-assigned this Aug 2, 2021
@yiliuTo
Copy link
Member

yiliuTo commented Aug 2, 2021

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@yiliuTo
Copy link
Member

yiliuTo commented Aug 3, 2021

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@yiliuTo yiliuTo left a comment

Choose a reason for hiding this comment

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

lgtm

@yiliuTo yiliuTo merged commit 26879b6 into Azure:main Aug 4, 2021
@zhichengliu12581 zhichengliu12581 deleted the enable-properties-which-supported-in-sdk branch August 24, 2021 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
azure-spring All azure-spring related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants