Whenever I try to (plan and) apply a Terraform file to create a VM with custom vcores / cores_per_processor / ram / hdds (so no preconfigured machine type, but a manually configured/customized machine), I get back the following error: 400 - Type: INVALID_PARAMETERS during execution/apply phase. The values provided do seem correct though.
Inspection of the API requests/responses seems to indicate that a required parameter server_type (that possibly needs to be set to cloud as opposed to baremetal?) might be missing in the request sent to the cloud Providers (REST) API. Could it be that the 1&1/ionos API has changed for this use-case, and that the Terraform provider needs to send an additional field to the 1&1/Ionos API? I tried to set the parameter manually in the Terraform-file, but it does not seem to be recognized in the planning-phase.
Whenever I try to (plan and) apply a Terraform file to create a VM with custom
vcores/cores_per_processor/ram/hdds(so no preconfigured machine type, but a manually configured/customized machine), I get back the following error:400 - Type: INVALID_PARAMETERSduring execution/apply phase. The values provided do seem correct though.Inspection of the API requests/responses seems to indicate that a required parameter
server_type(that possibly needs to be set tocloudas opposed tobaremetal?) might be missing in the request sent to the cloud Providers (REST) API. Could it be that the 1&1/ionos API has changed for this use-case, and that the Terraform provider needs to send an additional field to the 1&1/Ionos API? I tried to set the parameter manually in the Terraform-file, but it does not seem to be recognized in the planning-phase.