Problem with datadource google_certificate_manager_certificates

[mXtone]

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 --version
Terraform v1.9.5
on linux_amd64

• provider registry.terraform.io/hashicorp/google v6.4.0
• provider registry.terraform.io/hashicorp/google-beta v6.4.0
• provider registry.terraform.io/hashicorp/random v3.6.3

Affected Resource(s)

data.google_certificate_manager_certificates

Terraform Configuration

1 option:

data "google_certificate_manager_certificates" "cert" {
  project = var.project-id
  filter = "name:projects/${var.project-id}/locations/GLOBAL/certificates/cert"
}

2 option:

data "google_certificate_manager_certificates" "cert" {
  filter = "name:projects/${var.project-id}/locations/GLOBAL/certificates/cert"
}

Debug Output

No response

Expected Behavior

Create data object certificate

Actual Behavior

I got 2 errors:

1 option(error on validate):

│ 
│   on xxx.tf line xxx, in data "google_certificate_manager_certificates" "cert":
│  xxx:   project = var.project-id
│ 
│ An argument named "project" is not expected here.

2 option(error on plan):

│ 
│   with data.google_certificate_manager_certificates.certificate_calend_cloud,
│   on xxx.tf line xxx, in data "google_certificate_manager_certificates" "cert":
│  xxx: data "google_certificate_manager_certificates" "cert" {
│ 
I don't know if I'm doing something wrong or there's a bug in implementation.

Steps to reproduce

Use 1 option code with terraform validate command or use 2 code option with terraform plan command

Important Factoids

No response

References

No response