#terraform-tool

Hi guys, does anybody have any suggestions about how to define a VPC on AWS and multiple types of instances with different lifecycles that should be placed within this VPC

In other words, if I do a terraform apply or destroy I want that to apply to only a limited amount of resources whilst still being able to use the VPC properties with all the resources

Is my only option -target=resource?

simonvanderveldt: use remote modules

I.e. define your VPC in one place, and then export the state and pull it in in another place

t0m: Thx, didn't think of that :)

t0m: will that also work when you use remote state?

yarr :)

Allright, will give it a go then, thanks!

pmoust: not yet - you're waiting on that ELB regexp fix?

yeap.

No worries, we 'll distribute a binary to my team.

was hoping to start moving to atlas, as having the state in VCS is a PITA

vaguely guessing we'll probably try and cut something by end of next week with a batch of fixes.

;)

btw, is hashicorp remote-work-friendly?

yup https://hashicorp.com/jobs.html

HC engineering is remote-native

it'd be pretty neat to work for hashicorp

I'd have to learn more Go first, heh

soooo

how are the chefs in here getting around the chicken and egg problem with chef-vault + terraform?

problem is chef-vault requires a node be added to the ACL first... :(

svanharmelen: you around?