You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are migrating our backup to terraform and try to do it for dataview.
When we try to bind our already existing data view on our cluster and the terrafrom ressource, terraform don't find existing object with following error
│ Error: Cannot import non-existent remote object
│
│ While attempting to import an existing object to
│ "elasticstack_kibana_data_view.everything", the provider detected that no
│ object exists with the given id. Only pre-existing objects can be imported;
│ check that the id is correct and that it is associated with the provider's
│ configured region or endpoint, or use "terraform apply" to create a new
│ remote object for this resource.
Hello everyone,
we are migrating our backup to terraform and try to do it for dataview.
When we try to bind our already existing data view on our cluster and the terrafrom ressource, terraform don't find existing object with following error
│ Error: Cannot import non-existent remote object
│
│ While attempting to import an existing object to
│ "elasticstack_kibana_data_view.everything", the provider detected that no
│ object exists with the given id. Only pre-existing objects can be imported;
│ check that the id is correct and that it is associated with the provider's
│ configured region or endpoint, or use "terraform apply" to create a new
│ remote object for this resource.
We use following command to do it as mentionned on the doc :(https://registry.terraform.io/providers/elastic/elasticstack/latest/docs/resources/kibana_data_view)
terraform import elasticstack_kibana_data_view.my_data_view /
terraform import elasticstack_kibana_data_view.everything default/everything
In my cluster, I have a data view name Everything with id everything on the default space which id is default.
Is it bug ? or I don't import it well ?
The text was updated successfully, but these errors were encountered: