Add storage common property configuration supports all Storage features

[hui1110]

As title.
Add properties prefixed with spring.cloud.azure.storage, so that common properties such as account-name, connection-string, etc. can be shared.

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

spring-cloud-azure-autoconfigure
spring-cloud-azure-starter-storage

[hui1110]

#28461

[check-enforcer]

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

[hui1110]

/azp run java - spring - ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[hui1110]

/azp run java - spring - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[saragluna]

LGTM.

[saragluna]

Hi @alzimmermsft, we changed some annotations for some AutoConfiguration classes in this PR, which aren't breaking changes in Spring. But now it seems like the java-code-quality-reports-ci failed because of this https://dev.azure.com/azure-sdk/public/_build/results?buildId=1615699&view=results. But we marked these changes in the revapi.json file as exceptions. Do you know how to make the java-code-quality-reports-ci ignore them too?

[alzimmermsft]

Hi @alzimmermsft, we changed some annotations for some AutoConfiguration classes in this PR, which aren't breaking changes in Spring. But now it seems like the java-code-quality-reports-ci failed because of this https://dev.azure.com/azure-sdk/public/_build/results?buildId=1615699&view=results. But we marked these changes in the revapi.json file as exceptions. Do you know how to make the java-code-quality-reports-ci ignore them too?

At a quick glance the new ignores added to RevApi should be ignoring what is being reported, I'll need to take a deeper look to understand why this isn't happening.

[alzimmermsft]

Hi @alzimmermsft, we changed some annotations for some AutoConfiguration classes in this PR, which aren't breaking changes in Spring. But now it seems like the java-code-quality-reports-ci failed because of this https://dev.azure.com/azure-sdk/public/_build/results?buildId=1615699&view=results. But we marked these changes in the revapi.json file as exceptions. Do you know how to make the java-code-quality-reports-ci ignore them too?

At a quick glance the new ignores added to RevApi should be ignoring what is being reported, I'll need to take a deeper look to understand why this isn't happening.

I believe what is happening is that the code-quality-reports pipeline builds and installs the code-quality-reports library before downloading the DevOps cached Maven cache which overwrites any new changes if there was a cache hit. And the previous runs in the PR did have a cache hit.

This PR is fixing that with two changes:

• The Maven cache is cleaned before DevOps can cache it by removing all com.azure libraries.
• Installation of the code-quality-reports project happens after the cache is downloaded.

Both of these changes replicate what happens in the Analyze job, which isn't seeing the same failures.

[saragluna]

@alzimmermsft thanks!