Facilities can be specified by ID, but then resources are destroyed and recreated after the provider normalizes to names

[grahamc]

I wish I had a good log of this happening, but I created a spot market request in the facility c9dcbd06-6797-4096-b648-1be16dd5d833 (dfw2) and it worked correctly. I then applied again, and the plan included destroying all my spot market requests, and recreating them, because the provider recorded the actual facility as dfw2. Maybe a reasonable option here is rejecting UUID-based facilities?

[displague]

I'm sorry to hear that, @grahamc.

I don't know if it is possible to use the client to look up the facility UUID during theDiffSuppressFunc for facility, but that could be one approach.

https://registry.terraform.io/providers/equinix/metal/latest/docs/resources/device#facilities
The documentation for this field says that "facility codes" should be used, it would seem to fair to block UUIDs. Since any user that was using UUIDs would shared your experience, we shouldn't worry about backwards-compatibility in a solution for this, since facilities = [UUID] was never a working approach (beyond the initial provision).

[displague]

Closing this since it relates to a deprecated feature #312