This message was deleted.
# generals
sparse-intern-71089
07/15/2019, 7:23 PMThis message was deleted.
c
cuddly-eye-68174
07/15/2019, 7:24 PMSo I think the allocationid shoud be epialoc-blablabla
cuddly-eye-68174
07/15/2019, 7:24 PM🙂
cuddly-eye-68174
07/15/2019, 7:24 PMor both id and allocation id too
h
high-translator-22614
07/15/2019, 7:25 PMcan you see allocation IDs on the console?
c
cuddly-eye-68174
07/15/2019, 7:25 PMon AWS console?
h
high-translator-22614
07/15/2019, 7:25 PMyeah
c
cuddly-eye-68174
07/15/2019, 7:25 PMofc
h
high-translator-22614
07/15/2019, 7:25 PMdoes it have one?
high-translator-22614
07/15/2019, 7:25 PM(just trying to cover "AWS is being weird again")
c
cuddly-eye-68174
07/15/2019, 7:25 PMyes
cuddly-eye-68174
07/15/2019, 7:28 PMid is also good for me...just it was weird for me...when I wanted to deploy an NLB with fix ip
cuddly-eye-68174
07/15/2019, 7:36 PMwith eip.id works correctly
cuddly-eye-68174
07/15/2019, 7:38 PMMaybe it is only a small bug, the framework does not populate the alocationId property of the eip
w
white-balloon-205
07/15/2019, 11:07 PM
white-balloon-205
07/15/2019, 11:09 PM
https://github.com/terraform-providers/terraform-provider-aws/pull/7923 is a PR to fix this - but has been open in the upstream Terraform Provider repo for 4 months unfortunately 😞
c
cuddly-eye-68174
07/16/2019, 11:00 AMThanks Guys!