Resolve ConflictingBeanDefinition for DependencyLogger Bean and Upgrade reactor-core version in azure pom.xml

Type of change

• Bug Fix
• Feature

Does this introduce a change in the core logic?

• [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this introduce a breaking change?

• [NO]

What is the current behavior?

• DependencyLogger Bean specified without Qualifier annotation

What is the new/expected behavior?

• DependencyLogger Bean specified with Qualifier annotation to resolve conflict from azure-core-lib 0.17.0 version
• upgrade reactor-core-version to 3.4.6 to 3.4.21 for resolving compatible versions of the classes 'reactor.netty.http.client.HttpClientConnect$HttpObserver' and 'reactor.core.publisher.MonoSink'

Have you added/updated Unit Tests and Integration Tests?

NO

Any other useful information

To fix 'search-service' azure-deploy job failures in M14-Release 0.17

assigned to @thulasi_dass

added 7 commits

• a0c294e5...eb8af4eb - 5 commits from branch master
• 3a760003 - Resolve DependencyLogger Bean name conflict
• cc3b2637 - Merge branch 'az/td-fix-azure-deploy' of...

Compare with previous version

added 1 commit

• 55c5cd23 - Upgrade reactor-core version [Azure]

Compare with previous version

marked this merge request as ready

changed title from Draft: [Do Not Merge] Resolve DependencyLogger Bean name conflict to Resolve ConflictingBeanDefinition for DependencyLogger Bean and Upgrade reactor-core version in azure pom.xml

changed the description

changed milestone to %M14 - Release 0.17

added Azure label

requested review from @chad and @nursheikh

approved this merge request

mentioned in commit b801008f

merged

• Resolved azure-deploy & azure-test related failures and code changes are related to azure, Hence merging with master

mentioned in merge request !362 (merged)

added MRBugfix label