[BUG] Inconsistent Kubernetes Version Handling for "talos" Cluster Type in Terraform Provider after 1st apply [400 bad request] cluster is already at the requested version 1.x.z

[brokedba]

Description

I. What's the issue?

There is a bug in the Civo Terraform provider (version 1.1.4 or lower) related to the kubernetes_version parameter for the "talos" cluster type.

1. Initial Deployment:
Specifying kubernetes_version = "talos-v1.5.0" successfully deploys the cluster.

2. Subsequent apply Operations:
When making changes (e.g., adding nodes) and running terraform apply, the process fails with the following error:

Error: invalid Kubernetes version format: '1.27.0' for cluster type 'talos'.  
Please ensure your version matches the expected format, e.g., 'talos-vX.Y.Z'.  


Available versions for 'talos':  
- Stable: [talos-v1.5.0]  
- Development: []  

If I comment kubernetes_version . Removing the kubernetes_version line results in another error:

Error: [ERR] failed to update kubernetes cluster: Error: Unknown error response 
- status: 400 Bad Request, code: 400, 
- reason: {"code":"kubernetes_cluster_invalid_version_upgrade",
"reason":"The cluster cannot be upgraded with the given kubernetes version: this cluster is already at the requested version 1.27.0"}  

Root Cause:

There appears to be a mismatch between the format required for the initial deployment (talos-vX.Y.Z) and the API's metadata response (1.27.0).

Impact:
This results in an inability to apply any updates to the cluster. The only workaround is to destroy and recreate the cluster, which is inefficient and frustrating.

2. Steps to reproduce it

• Deploy a "talos" cluster using Terraform:

resource "civo_kubernetes_cluster" "talos_cluster" {  
  name                = "example-cluster"  
  kubernetes_version  = "talos-v1.5.0"  
  nodes               = 3  
  ...  
}  

1. Run terraform apply .
   The cluster deploys successfully.
2. Add any update (e.g., increase node count, add helm deployment) and run terraform apply again.
   result > The error regarding the invalid Kubernetes version appears.
3. Comment out the kubernetes_version parameter and run terraform apply.
   result > The second error occurs, preventing updates.

3. Additional information

Related Issue: This behavior seems similar to the data source issue reported in #363.

It has been very frustrating to have to destroy all deployments in order to add a resource.
second apply change Screenshots:

Acceptance Criteria

Provide a Fix:
Ensure that the Terraform provider properly handles the Kubernetes version for "talos" clusters across all operations (apply, plan, and destroy).
Update the control logic to:

1. Accept the talos-vX.Y.Z format consistently.
2. Prevent metadata overwrite issues that cause subsequent apply operations to fail.

[uzaxirr]

Hey the team is working on this as we speak

[brokedba]

@uzaxirr thanks I thought it'd be better to create an issue instead of a random chat in slack support channel.
please keep me posted.