Local Docker build fails when amazon-blc module is added to pom

[frostyandy2k]

A Brief Overview

I have encountered an issue with the amazon-blc module.
It creates a bean no matter if we need it or not and in turn tries to see if there are any valid credential providers. This causes the admin and site to crash in a local docker container:

admin_1    | Error: Failed to list store contents: NoCredentialProviders: no valid providers in chain. Deprecated.
admin_1    | For verbose messaging see aws.Config.CredentialsChainVerboseErrors
 
shopping-cart_admin_1 exited with code 1
site_1     | Error: Failed to list store contents: NoCredentialProviders: no valid providers in chain. Deprecated.
site_1     | For verbose messaging see aws.Config.CredentialsChainVerboseErrors

[frostyandy2k]

¡ this may be due to something else in our system !

Will add updates shortly.

[frostyandy2k]

BLC does not crash in a docker environment when adding the amazon-blc module. The issue was due to runtime executable that wrongly interpreted the AWS_ACCOUNT_ALIAS variable.

Still, it would be useful to be able to toggle the module on or off for local testing as is done in this PR.