Comment on Terraform Gotchas and How We Work Around ThemparentComments−sevagh9yWe ran into similar issues. From there I went one step further and wrote a tool to do the attachments for me (instead of using Terraform's aws_volume_attachment):https://github.com/sevagh/goatThis way in Terraform I provision a group of volumes, a group of instances, and rely on `goat` to do the rest.−kalmarOP9yThat's pretty cool. So is the model that you don't manage the volumes in TF at all?(Btw I think I know people you know... also in Montreal and I know a couple folks at AdGear!)−sevagh9yThat's cool, I'll ask my coworkers.And yes this way I keep EBS and the rest of my recipes as far away as possible.Something like:``` kafka-volumes/ <ebs volumes> terraform.tfstate kafka/ (use local backend ../kafka-volumes/terraform.tfstate) <ec2 instances> ```
Comments
We ran into similar issues. From there I went one step further and wrote a tool to do the attachments for me (instead of using Terraform's aws_volume_attachment):
https://github.com/sevagh/goat
This way in Terraform I provision a group of volumes, a group of instances, and rely on `goat` to do the rest.
That's pretty cool. So is the model that you don't manage the volumes in TF at all?
(Btw I think I know people you know... also in Montreal and I know a couple folks at AdGear!)
That's cool, I'll ask my coworkers.
And yes this way I keep EBS and the rest of my recipes as far away as possible.
Something like:
``` kafka-volumes/ <ebs volumes> terraform.tfstate kafka/ (use local backend ../kafka-volumes/terraform.tfstate) <ec2 instances> ```