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

Modify spring-cloud-azure-core, spring-cloud-azure-service, and spring-cloud-azure-resourcemanager according to API review comments #25851

Conversation

saragluna
Copy link
Member

@saragluna saragluna commented Dec 7, 2021

The spring-cloud-azure-core is being reviewed by the architects, this PR is to apply the changes according to comments.

spring-cloud-azure-core: spring-cloud-azure-core (version 4.0.0-beta.3) - apiview.dev
spring-cloud-azure-service: spring-cloud-azure-service (version 4.0.0-beta.3) - apiview.dev
spring-cloud-azure-resourcemanager: spring-cloud-azure-resourcemanager (version 4.0.0-beta.3) - apiview.dev

@ghost ghost added the azure-spring All azure-spring related issues label Dec 7, 2021
@azure-sdk
Copy link
Collaborator

API changes have been detected in com.azure:azure-core. You can review API changes here

@azure-sdk
Copy link
Collaborator

API changes have been detected in com.azure:azure-core-management. You can review API changes here

API changes

-         public static final Region SWEDEN_CENTRAL = new Region("swedencentral", "Sweden Central");

@check-enforcer
Copy link

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

@saragluna saragluna changed the title Modify spring-cloud-azure-core and spring-cloud-azure-service according to API review Modify spring-cloud-azure-core, spring-cloud-azure-service, and spring-cloud-azure-resourcemanager according to API review comments Dec 20, 2021
@@ -129,14 +129,14 @@ public Processor getProcessor() {
/**
* Properties of an Event Hub producer.
*/
public static class Producer extends AzureEventHubsCommonProperties implements EventHubsProducerDescriptor {
public static class Producer extends AzureEventHubsCommonProperties implements EventHubProducerProperties {
Copy link
Member

Choose a reason for hiding this comment

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

need we rename EventHubsProducerDescriptor to EventHubProducerClientProperties?

Copy link
Member Author

Choose a reason for hiding this comment

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

Given Event Hubs only have one client builder, EventHubClientBuilder, so we won't call it EventHubProducerClientProperties.


}

/**
* Properties of an Event Hub consumer.
*/
public static class Consumer extends AzureEventHubsCommonProperties implements EventHubsConsumerDescriptor {
public static class Consumer extends AzureEventHubsCommonProperties implements EventHubConsumerProperties {
Copy link
Member

Choose a reason for hiding this comment

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

need we rename EventHubsConsumerDescriptor to EventHubConsumerClientProperties?

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

@saragluna
Copy link
Member Author

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@saragluna
Copy link
Member Author

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@saragluna saragluna merged commit 9048cd1 into Azure:feature/azure-spring-cloud-4.0 Dec 24, 2021
@saragluna saragluna deleted the xiada/feature/spring-cloud-azure-apiview branch March 17, 2022 05:27
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.

3 participants