#terraform-tool

stephent, I think even with ENV vars it requires a blank vars file :\

but I don't use env vars at all

stephent: hmm yeah that looks like it should work

I’ve just checked my version of terraform which is 0.4.2 - odd. Perhaps that’s it. Will install 0.5.1

Hey all, I'm trying out terraform 0.5.3's new aws_volume_attachment feature. If I have something like this: http://hastebin.com/urawowaxin.json. Then the instance gets a default ebs on /dev/xvda volume when it starts, and vol-1-attach fails. Is there any way around getting that default volume?

kmorgan: because aws_volume_attachment happens after instance launch, i think you can't avoid the volumes that come with the instance - you have to use ebs_block_device and friends

stephent: 0.5.3 but +1 :)

ah… yes - brew cask was out of date

sounds good phinze; thanks for the help; if I or a team member of mine has time to start that PR we'll submit a quick proposal for you guys to sign off on it

great! thanks ctiwald

phinze: can I use ebs_block_device, or do I need root_block_device? The reason I want to use aws_volume_attachement is because the ebs volumes stick around after instance termination, and can be migrated to other instances. I don't think I get that with ebs_block_device or root_block_device. Does that make sense?

kmorgan: ah wasn't sure if you were trying to replace the root device - yeah gotchya.

so i think the best you can do is https://terraform.io/docs/providers/aws/r/insta...

^ use root_block_device and set delete_on_termination to false

you won't have a direct reference to the volumes from tf

but they won't be nuked

Is the volume id persisted anywhere that I can query?

within terraform? i don't believe so at the moment... you'd have to drop down to something like awcli

so yes, my version of terraform was the issue - D’oh! thanks for your input any way guys

phinze: That's too bad :( thanks for the help.

kmorgan: np - feel free to file an issue describing your use case and any ideas you have about how TF could support it

phinze, did you see my template workaround? :P

I should have called it "dirty_template.tpl"

if I use terraform apply -target=foo.bar, but foo.bar doesn't match any defined resources, should one expect it to apply all changes or no changes?

buckaroo: i'd expect it to apply no changes, but `terraform plan -target=foo.bar` will tell you for sure what will happen

ah, `terraform -target=foo.bar plan` is not the same, and does not work as expected.

what consumed the -target= flag in that case?

buckaroo: ah yes - we've filed that upstream at mitchellh/cli and it's been recently fix, should return a sane error msg in next version

*fixed

supercool thanks