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

Remove validation dependency #25335

Merged
merged 16 commits into from
Nov 17, 2021
Merged

Remove validation dependency #25335

merged 16 commits into from
Nov 17, 2021

Conversation

backwind1233
Copy link
Contributor

@backwind1233 backwind1233 commented Nov 11, 2021

This PR is mainly about

  1. Remove the validation dependency spring-boot-starter-validation to simplify module dependency.
  2. Add a new starter -- spring-cloud-azure-starter-data-cosmos
Spring artifact Id Dependency
spring-cloud-azure-starter-cosmos azure-cosmos
spring-cloud-azure-starter-data-cosmos azure-spring-data-cosmos

@ghost ghost added the azure-spring All azure-spring related issues label Nov 11, 2021
@backwind1233
Copy link
Contributor Author

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@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

@backwind1233
Copy link
Contributor Author

/azp run java - spring - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@saragluna
Copy link
Member

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@backwind1233
Copy link
Contributor Author

/azp run java - spring - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

…dency_gzh

# Conflicts:
#	sdk/spring/spring-cloud-azure-starter-cosmos/pom.xml
throw new AADB2CConfigurationException("Sign in user flow key '"
+ loginFlow + "' is not in 'user-flows' map.");
}
if (!isValidURL(logoutSuccessUrl)) {

Choose a reason for hiding this comment

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

This should move into validateURLProperties?

if (!isValidURL(logoutSuccessUrl)) {
throw new AADB2CConfigurationException("logout success should be valid URL.");
}
if (!isValidURL(baseUri)) {

Choose a reason for hiding this comment

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

In original logic, baseUri can be empty, but now it can't.

*/
private void validateURLProperties() {
if (!CollectionUtils.isEmpty(userFlows)) {
if (!StringUtils.hasText(tenant) && !StringUtils.hasText(baseUri)) {

Choose a reason for hiding this comment

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

!StringUtils.hasText(tenant) is not belong to validateURLProperties. The method name will make the code confusing.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated

@backwind1233
Copy link
Contributor Author

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@saragluna
Copy link
Member

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

* @param uri
* @return whether is uri is valid or not.
*/
private boolean isValidURL(String uri) {
Copy link
Member

Choose a reason for hiding this comment

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

this should be a more common util, thus should be located in a util class in core , this properties class is not the proper place

@stliu
Copy link
Member

stliu commented Nov 16, 2021

A PR should contains one thing, apperently this PR does alot more than what the title / description said

@backwind1233
Copy link
Contributor Author

/azp run java - spring - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@azure-sdk
Copy link
Collaborator

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

API changes

+     public enum ErrorOptions {
+         THROW,
+         NO_THROW;
+     }
+         public RequestOptions setErrorOptions(EnumSet<ErrorOptions> errorOptions) 

@backwind1233
Copy link
Contributor Author

/azp run java - spring - tests

@backwind1233
Copy link
Contributor Author

/azp run java - spring - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

1 similar comment
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@backwind1233 backwind1233 merged commit 3570c2f into Azure:feature/azure-spring-cloud-4.0 Nov 17, 2021
@backwind1233 backwind1233 deleted the 211111_updatedependency_gzh branch November 17, 2021 06:59
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.

5 participants