bucket: Provider produced inconsistent final plan

[tormath1]

trafficstars

Terraform Version

$ terraform version
Terraform v1.7.5
on linux_amd64
+ provider registry.terraform.io/hashicorp/template v2.2.0
+ provider registry.terraform.io/poseidon/ct v0.11.0
+ provider registry.terraform.io/scaleway/scaleway v2.38.2

Affected Resource(s)

• scaleway_object_bucket
• scaleway_instance_snapshot

Terraform Configuration Files

It's almost the same code as in the documentation.

resource "scaleway_object_bucket" "bucket" {
  name = "snapshot-flatcar-import"
}

resource "scaleway_object" "qcow" {
  bucket = scaleway_object_bucket.bucket.name
  key    = "flatcar_production_scaleway_image.qcow2"
  file   = var.flatcar_file
}

resource "scaleway_instance_snapshot" "snapshot" {
  type = "unified"
  import {
    bucket = scaleway_object.qcow.bucket
    key    = scaleway_object.qcow.key
  }
}

resource "scaleway_instance_volume" "from_snapshot" {
  from_snapshot_id = scaleway_instance_snapshot.snapshot.id
  type             = "b_ssd"
}

Debug Output

╷
│ Error: Provider produced inconsistent final plan
│
│ When expanding the plan for scaleway_instance_snapshot.snapshot to include new values learned so far during
│ apply, provider "registry.terraform.io/scaleway/scaleway" produced an invalid new value for
│ .import[0].bucket: was cty.StringVal("snapshot-flatcar-import"), but now
│ cty.StringVal("fr-par/snapshot-flatcar-import").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Expected Behavior

The bucket name is consistent.

Actual Behavior

The bucket name is not consistent so TF is lost.

Steps to Reproduce

1. terraform apply

References

• https://github.com/flatcar/flatcar-terraform/pull/20

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