Previously the use_eip variable wasn't actually used to determine if an Elastic IP should be created or not. The Elastic IP resource now checks for var.use_eip.
Since use_route53 and the DNS record assumes the Elastic IP is available, also make sure both var.use_route53 and var.use_eip are true when creating the DNS record.
Finally, this also make the Elastic EIP id a module output for the scenario where an EIP is wanted but no DNS but still need access to the EIP created by the module.
Previously the
use_eipvariable wasn't actually used to determine if an Elastic IP should be created or not. The Elastic IP resource now checks forvar.use_eip.Since
use_route53and the DNS record assumes the Elastic IP is available, also make sure bothvar.use_route53andvar.use_eiparetruewhen creating the DNS record.Finally, this also make the Elastic EIP id a module output for the scenario where an EIP is wanted but no DNS but still need access to the EIP created by the module.
NOTE: This assumes PR #6 is merged first.
fixes #5