Thanks for the suggestion, we'll look into it.

A potential problem is that there are some inherent limitations due to the fact that we're executing things locally. For instance, the ELB CreateLoadBalancer API method returns a DNS name, which will require some adjustments to the tests if they are executed locally: http://docs.aws.amazon.com/elasticloadbalancing/2012-06-01/APIReference/API_CreateLoadBalancer.html#API_CreateLoadBalancer_ResponseElements
Potential solutions that come to mind would be to 1) have the tests send requests to localhost and send along a Host: ... HTTP header with the DNS name which allows the ELB mock to look up the corresponding backend service, or 2) actually update the /etc/hosts configuration file on the test machine (which typically requires root access and is therefore not really an option).

Another aspect to consider is that, if we want to support LocalStack ELB in Docker mode, we need to find a reliable way to forward any invocations hitting the ELB mock inside the Docker container to target services running outside the container (on the host operating system, or potentially in another Docker container running in parallel).

So there are a couple of things to consider if we want to add generic support for ELB/ALB. Did you have any particular use case in mind? Would be great to have a starting point, maybe an existing unit/integration test?

Uh oh!

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions