Fix AutoConfigureAfter for SecretsManagerAutoConfiguration #1235
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📢 Type of change
📜 Description
Fixes #1232
In version 3.2.0 SecretsManagerAutoConfiguration was added that requires bean
AwsClientBuilderConfigurer
, butSecretsManagerAutoConfiguration
didn't addedAwsAutoConfiguration
inAutoConfigureAfter
instead ofCredentialsProviderAutoConfiguration
andRegionProviderAutoConfiguration
.💡 Motivation and Context
@AutoConfigureAfter({ CredentialsProviderAutoConfiguration.class, RegionProviderAutoConfiguration.class }) was added to
AwsAutoConfiguration
, andAwsAutoConfiguration
was put as prerequisite forSecretsManagerAutoConfiguration
.💚 How did you test it?
Added
AwsAutoConfigurationTests
file.📝 Checklist
🔮 Next steps