container: missing region field when importing a cron

[norbjd]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

• Terraform v1.7.0
• provider registry.terraform.io/scaleway/scaleway v2.36.0

Affected Resource(s)

• scaleway_container_cron

Terraform Configuration Files

terraform {
  required_providers {
    scaleway = {
      source  = "scaleway/scaleway"
      version = "2.36.0"
    }
  }
}

provider "scaleway" {}

resource "scaleway_container_cron" "test" {
  name = "test"
}

Expected Behavior

After terraform importing a scaleway_container_cron, the region field should be set to the cron's region.

Actual Behavior

After terraform importing a scaleway_container, the region field is null.

So, if we run terraform apply after importing, Terraform will try to recreate the scaleway_container_cron resource.

Steps to Reproduce

1. create a container cron (outside Terraform)
2. import the cron with terraform import scaleway_container_cron.test fr-par/11111111-1111-1111-1111-111111111111
3. check the region field: jq '.resources[] | select(.name == "test") | .instances[0].attributes.region' terraform.tfstate

References

• for scaleway_function, the missing region have been added here: function: missing fields in Read #2364. I guess this is the same issue, but for containers, and it only affects region