[FEATURE] Allow to use ovh_cloud_project_volume as a resource

[kyngs]

Description

I would like to configure my block volumes using Terraform. Currently, there's only a data source for ovh_cloud_project_volume, but not a resource.

Affected Resource(s) and/or Data Source(s)

• ovh_cloud_project_volume

Potential Terraform Configuration

Something like:

resource "ovh_cloud_project_volume" "volume" {
  service_name    = "your_project_id"
  region          = "DE" 
  name            = "my-volume"
  size            = 10  # Size in GB
  type            = "classic"
}

Additional context

I feel like this is intentional, why? To prevent accidental data loss?

[amstuta]

Hello @kyngs,

In fact the resource to handle volumes exists, it is just named a bit differently because it is based on the region-centric API routes in the /cloud section.

Here is the resource documentation: https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_region_volume

Is it what you were looking for ?

[kyngs]

Hello @kyngs,

In fact the resource to handle volumes exists, it is just named a bit differently because it is based on the region-centric API routes in the /cloud section.

Here is the resource documentation: https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_region_volume

Is it what you were looking for ?

Hi, thanks for the quick response.
This resource really does seem like what I was looking for, not sure how I missed it. Tho its category seems odd.
I've got a new question: why does changing the size of the volume force a replace? The administration panel allows me to expand the volume without deleting it.

[amstuta]

You're right, the category makes no sense and will be fixed soon!

Regarding the size update, it has not been implemented yet in the provider as it requires a separate API call to POST /cloud/project/{serviceName}/volume/{volumeId}/upsize. We will add this call in the provider shortly.