#terraform-tool

super excited about the ecs stuff

anyone dealt with this? * ClusterContainsContainerInstancesException: The Cluster cannot be deleted while Container Instances are active.

would depends_on affect order of destruction?

ryangg: yep it should. the dependencies chain is walked backwards for destruction

sweet I'll try that. maybe killing the nodes first will make it easier to kill the ecs cluster. :)

yep - if you run into any hiccups feel free to open an issue with some config snippets - always happy to talk something out on an issue thread

phinze: that worked brilliantly and now I can destroy ECS clusters. Thanks!

hooray!

has anyone else seen a bug where you get a error about an aws security group having a dependent object, even though that security group should not be getting any updates?

hey folks. trying out terraform for the first time, and loving it. has anyone had an issue trying to create an AWS elasticache cluster? i get `Error creating Elasticache: InvalidParameterCombination: Cluster can only be created in a VPC` - is this generally the case for terraform with elasticache?

never mind - just using the wrong instance type

hm...I'm having some trouble with a couple of route table associations. I'm doing a typical public/private subnet split with the correspondng routes. the public routes come up fine, but the private routes fail.

gist: https://gist.github.com/pikeas/7cfa0bb3555ee3b1...

Various other resource creation bits removed, these should be the only relevant bits.

knite: could you pastebin an example config?

nothing jumps out from the output

maybe look at the route table associations that were set up and see if anything seems off

_jesse_: comparing against someone else's terraform config post, I tentatively think that one route table for two public subnets is okay, but I need a separate table per private subnet?

at any rate, that's the main difference between my config and this example config. I don't understand why that would be necessary, but I'm trying it...

I think one route table should be fine

I write my config in YAML - are you cool with a YAML paste, or would you prefer the JSON I pass to terraform?

JSON would probably be preferrable just so I can try to run it

hokay, that's a bit trickier, what with separate variable file, etc. let me gin up a minimal repro I can share.

that would be perfect, I can eyeball your YAML, but it'd be easiest to see what's up with something I can execute

_jesse_: okay, got a trimmed down repro. this uses us-east-1, I can pull up the AMI for a different region if you need it. all you'll need is an existing key pair name you can use, and being cool with spinning up a t2.micro for a minute or 5. and even that can probably be replaced with an internet gateway and still repro.

_jesse_: https://gist.github.com/pikeas/e5d1f1caf96d8689...

this is supposed to be a pretty bog standard setup, I'm not sure why it's failing.

_jesse_: any thoughts?

sorry, stepped away for a moment, looking now

knite: for your private subnet association, you have '"subnet_id": "${element(aws_subnet.public.*.id, count.index)}"'

I think you mean to have aws_subnet.private

doh!

:)

good morning

Hey dudes/dudettes

Any ETA for 0.6.1?