Closed displague closed 3 years ago
how should userdata changes trigger the device to reprovision? Should this be indicated with spec level (not forProvider level) options? crossplane/crossplane#2258
There are parallels to this question in https://github.com/packethost/terraform-provider-packet/issues/77 where the intent to reprovision an existing device is desired, without DELETE
'ing the resource. Some otherwise immutable features become mutable through EM API /device/{id}/actions
.
This PR has a few incomplete changes to incorporate for #54:
make run
)TODO:
how should userdata changes trigger the device to reprovision? Should this be indicated with
spec
level (notforProvider
level) options? https://github.com/crossplane/crossplane/issues/2258Update: this is less destructive with
POST /devices/{id}/actions { "type": "reinstall" }
https://metal.equinix.com/developers/docs/resilience-recovery/reinstall/