fmcgeough / ex_aws_elastic_load_balancing Goto Github PK

The type definition for target_description:

 @type target_description :: [
          id: binary,
          port: integer,
          availability_zone: binary
        ]

only allows a keyword list, and with Dialyzer involved this means writing something like [[id: "foo"]] to satisfy the type. However, the actual allowed data is a keyword list or a map (and I guess maybe other things) and the examples use either maps or a naked ID (I'm not sure that the latter will work with the API though) for register/deregister.

Reason I'm submitting in issue first and not a PR right away is that I'm not sure whether the typespec should be changed/widened up or whether the examples should be adapted - more than happy to do either after a decision :)

(Hi, Frank!)

I didn't see this mentioned elsewhere, so I wanted to confirm my hypothesis. I currently have 3 entries on the Load Balancers section of my AWS admin: 2 are classics and one is an ALB. When I call describe_load_balancers() I only receive information on the ALB. I found a note in some AWS documentation indicating that the old and new ELB types might be accessible via different API versions. Is this expected behavior?

Are you planning on publishing this library to hex or will it always be a github install?