Add ability to override AWS endpoints during configuration discovery.

[ammeek]

Currently, it is not possible to override the AWS SSM/ secret manager endpoint during configuration discovery. This stops you from being able to integrate Localstack during the configuration discovery process.

I've added the BootstrapContextCompatible annotation to the AWSServiceConfigurationProperties class to resolve this.
I've also added a test to check that this annotation has been added as I have seen similar tests throughout the project.
I am not sure if additional testing showing the configuration discovery process integrating with Localstack is required.

[CLAassistant]

All committers have signed the CLA.

[sdelamo]

@ammeek I am not sure we need this pull-request. I think you can create a BeanCreatedEventListener for the different builders builder.

e.g

@Singleton
public class S3ClientBuilderCustomizer implements BeanCreatedEventListener<S3ClientBuilder> {

    @Override
    public S3ClientBuilder onCreated(@NonNull BeanCreatedEvent<S3ClientBuilder> event) {
        return event.getBean()
            .overrideConfiguration(c -> c.apiCallTimeout(Duration.of(60, ChronoUnit.SECONDS)));
    }
}

[ammeek]

Thanks for your reply @sdelamo unfortunately, the bootstrap context disallows bean event listeners.

I would like to be able to continue to use the established convention for overriding AWS endpoints in Micronaut which is done via the AWSServiceConfigurationProperties class. This PR will allow that class to be available during configuration discovery via the bootstrap context.

[sdelamo]

@ammeek the motivation for this is because you need to inject AWS SDK beans in your bootstrap aware code? or is to test an integration such as secrets manager which runs at bootstrap.

[ammeek]

@sdelamo Yea the motivation for this is to test an integration with secrets manager/param store at bootstrap.