Closed whummer closed 7 years ago
@vbudilov @dpantke Is this PR being considered, any chance we can get this merged? Thanks!
Hi @whummer,
Thanks for the PR! I'm reviewing it now and will get back to you soon.
Vladimir
Hi @whummer ,
I've done a bit of digging and think that instead of a code PR it would be beneficial for our users to add an additional section to the README file to describe ways to test this app locally. There are many such frameworks. I want devs to know what options they have, with LocalStack being one of them.
So you can create a "Local Testing" header, with a "LocalStack" subsection underneath. How does that sound?
Thanks for the feedback @vbudilov , really appreciated! The README has been updated with instructions for local testing, as per your suggestion.
I still believe that the ability to specify target endpoints is highly valuable for the users. You are right that there are different frameworks for local testing (LocalStack being one of them), but they all equally benefit from the ability to customize the service endpoints. I've made sure in the PR that the changes are as generic as possible, but if you feel that the code could be improved, I'd be happy to follow up with changes to accommodate any specific concerns. Thanks again.
This PR enables configuration of custom service endpoints.
Specifying custom endpoints in the AWS SDK is an extremely useful feature for testing. The main motivation for this change is to make the sample application work with LocalStack (a local AWS testing/mocking service).
In particular, this change enables: 1) using a custom CLI command (
awslocal
instead ofaws
) 2) using local service endpoints instead of the AWS production endpointsThe application can be initialized using the
awslocal
CLI (https://github.com/localstack/awscli-local) to use the local service endpoints:Note that this is a non-breaking change that fully maintains backwards compatibility. The
$aws_cmd
variable defaults toaws
, and by default the application still uses the production AWS services.