google_network_security_url_lists name change bug

[syubuntu]

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 me too comments, 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.
• If an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Terraform Version & Provider Version(s)

Terraform v1.9.5 on linux_amd64

• provider registry.terraform.io/hashicorp/google v6.5.0

Affected Resource(s)

google_network_security_url_lists

Terraform Configuration

before change code:

resource "google_network_security_url_lists" "default" {
  name     = "my-url-lists"
  location = "us-central1"
  values   = ["www.example.com"]
}

note: This code is same as basic example of below.
https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/network_security_url_lists#example-usage---network-security-url-lists-basic

after change code:

resource "google_network_security_url_lists" "default" {
  name     = "my-url-lists-renamed"
  location = "us-central1"
  values   = ["www.example.com"]
}

Debug Output

No response

Expected Behavior

forces replacements happens because UrlList name is immutable.

• delete "my-url-lists" UrlList
• re-create "my-url-lists-renamed" UrlList.

Actual Behavior

The below error occurs. No change happens to "my-url-lists".

│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to google_network_security_url_lists.default, provider
│ "provider[\"registry.terraform.io/hashicorp/google\"]" produced an unexpected new value: Root object was present, but now
│ absent.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Steps to reproduce

1. terraform apply with before change code.
2. change the code to after change code.
3. terraform apply with after change code.

Important Factoids

No response

References

No response

b/372044327

[ggtisc]

This looks like incorrect behavior. In my case I tried to reproduce the issue. Although I didn't get an error, a new resource was created without deleting the existing one which is also not something to expect. I'm forwarding it for a more in-depth review