#terraform-tool

Specifically the "Multiple Provider Instances" section TaiSHi

I messed up a bit ago with a terraform refresh

so you can give one provider an alias

like "west"

Not what I was looking for but that's actually COOL.

and then you add 'provider = "aws.west"'

to any resource you want to use it in

I mean I have a couple customers + my day job

so you can actually have one set of configuration which applys to like 4 different AWS accounts.

Was testing aws credential profiling and cleaned up my state

So got a lot of orphaned resources

I think if you use a combination of 'count' and 'lookup' you may be able to dynamically set the 'provider' arg on a resource.

So you can create the same resource in 4 different aws accounts, with one TF config :)

Hmm I might come back to that later on

But right now dealing with finishing IMPOSING terraform on my job

Boss is on vacation, just replaced half of CF templates for TF :P

TaiSHi: I have no idea if this works ... https://gist.github.com/tecnobrat/d1ecbc3b673a1...

it may, it may not.

*shrug*

Might be, but my issue was something else

I think I can say it like this

I have a resource (sg-123456) created on account A

But if I change creds to match account B, it wont give a warning about being unable to 'use' or 'refresh' that resource

I probably wouldn't mashup separate accounts like that... feels risky

abtreece: was testing some scenarios

Helps prepare for the worst

I certainly agree with that, but I wouldn't do testing things in a directory of TF configs that are production

This hasn't gone in production yet

Can I exclude some files?

TaiSHi: use allowed_account_ids in the provider to stop yourself from being able to screw it up

Worries me that if I change the keypair for an instance

It'll delete it

Is anybody in here using Terraform with a provisioner to configure administrator password for new AWS instances?

(Windows* instances)