Confession: I can't really use #terraform
Anyway... I still think it's a bad tool. Or people use it wrong. For all the tasks where you want (need to) iterate / loop / generate secrets/, It's just bad & I don't like it...
... oh and don't even get me started on the inability to consolidate the state with changes in the remote resource on it's own...
@ondrejkolin I think this may be a limitation which comes from cloud providers APIs. On AWS I can do "terraform plan", check differences and update the config. I agree that sometimes this is not sufficient.
@weylandyutanicorp we're using azure quite heavily and my experience is, that if the cloud resource is changed manually to hot fix something (or whenever) the state file doesn't match anymore and it's super annoying...
Sure it's not really comparable, but ansible is respecting the current state and tries to push it in the right direction. (There are other issues in the end)
But I am a consumer of my company upstream, so I might be lacking the large picture ...