#terraform-tool

Hi, I am having trouble with the "connection" provisioner

it says that my key_file ~/.ssh/xyz.pem cannot be found

But cat ~/.ssh/xyz.pem shows otherwise

What gives?

Is connector trying to find that .pem file on the remote? No right?

jasonkuhrt_: I've been having a similar error, though not quite. Have you tried using an absolute path instead of a relative (`/home/you/whatever.pem` instead of `~/`)?

girvo: No, I will try that now though, second

girvo: Hm, that seemed to have worked...

girvo: Actually unconfirmed

girvo: It seems that because I was updating (+/-) not creating from scratch it did not run the remote-exec block

That is correct?

jasonkuhrt_: unfortunately I'm the wrong person to ask, i'm very new to Terraform too :) I'm having issues getting it to pick up my key pairs when creating AWS instances under VPC :(

Is it possible to name an AWS instance through Terraform? Also, there are 500 errors when trying to provision a t2.micro on ap-southeast-2 due to AWS being over capacity, but terraform just chokes on it instead with a 500 :(

also, is it possible to get terraform to run a provisioner after it's been created with `terraform apply`? The instance exists and it's working fine, but I added a provision block and it says that it's still the same

Is there any way to change the order when a resource is destroy? for example, if I change an instance and that change require the instance to be destroyed, I would prefer that the new instance gets created first and then destroy the other one.

blackjid: hm, no way to configure that, no. What's your use case?

a simple case would be instance and elastic IP, doing destroying at the end would enable me to have ~zero downtime, because it would create the new instances, change the registered instance on the elastic ip, and the destroy the original.

blackjid: interesting

@pearkes :) do you want me to add an issue in the terraforms github?

Yea sure!

done

awesome, thanks

hey @pearkes don you know when tagging instances is coming?

No known timeline, no, but it's not overly complex so shouldn't be loneg

long*