Releases: cloudposse/terraform-aws-ec2-instance
Releases · cloudposse/terraform-aws-ec2-instance
0.9.0 Remove `network_interface_id` output
what
- Remove
network_interface_idoutput
why
- No longer supported https://www.terraform.io/docs/providers/aws/r/instance.html
- Closes #37
0.8.0 Use `owners` with `data.aws_ami.info`
what
- Use
ownerswithdata.aws_ami.info
why
- The latest
terraform-aws-providerappears to require this, either supply it in case we're using the default AMI, or allow the user to provide it
0.7.6 Update readme yaml file and rebuild md
what
- updated
README.yamlfile - add tags and categories
- rebuild
README.mdfile
why
- need to add categories and tags so we can pull them into the documentation
Regenerate README.md
what
- Regenerate
README.md
why
- Previous version of build-harness has some typos
Migrate to README.yaml format
what
- Add
README.yaml
why
- Standardize README
0.7.3
0.7.2
what
- Remove
mapfrom the tags
why
mapsin dynamically calculatedcountsintroduce circular dependencies across TF modules
references
hashicorp/terraform#13980
hashicorp/terraform#10857
hashicorp/terraform#12570
hashicorp/terraform#17048
I know this issue has been discussed time and again (Ex: #12570) and that if a module has a map variable and has interpolation inside this map variable, count inside a module results in value of ‘count’ cannot be computed. What puzzles me is that this error occurs when terraforming a new environment but not any existing environment!
0.7.1
0.7.0
Allow associating a public IP to the instance without assigning an Elastic IP
what
- Allow associating a public IP to the instance without assigning an Elastic IP
why
- To separately control public and Elastic IPs
- A public IP could be associated to the instance without assigning an Elastic IP