Read Datastream upon `resource_already_exists_exception` about terraform-provider-elasticsearch HOT 2 OPEN

Hi @applike-ss, thanks for opening an issue. Unfortunately, I think this would generally break expectations of how terraform is supposed to work, for example, this could result in unintentionally overriding an existing data stream if the name collides.

Have you considered importing the resource into terraform?

from terraform-provider-elasticsearch.

Hi @phillbaker, yes i considered it. However it is not desirable in an automatically created environment to manually import things into a state. Right now it seems we can only create the datastream before making use of our module that creates all other monitoring related resources or we have to split our module in 2 parts. One part would run before and another one would run after the application was spawned.

Anyhow, i have seen somewhere in the terraform-provider-aws that upon resource creation it was imported when it did already exist. Not sure which one, but might be due to API limitations on aws side (like SNS topics, which can not be fetched by name).

I see that you don't want to break how terraform has worked for you until now and it makes sense to be able to detect when a resource i want to create did exist before (just not in the state). So feel free to close this one if you agree.

from terraform-provider-elasticsearch.