Skip to content

google_memorystore_instance dependency on "region" from provider level instead of "location" at resources level #23543

@damontfgz

Description

@damontfgz

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)

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

Affected Resource(s)

google_memorystore_instance

Terraform Configuration

Debug Output

Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: Cannot determine region: set in this resource, or set provider-level 'region' or 'zone'.

Expected Behavior

the memorystore should be able to recognize the region through the location field

However, the latest provider release 6.43.0 seems to be introducing a dependency on region at provider level, instead of honoring the location provided at resource level for google_memorystore_instance

Actual Behavior

Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: Cannot determine region: set in this resource, or set provider-level 'region' or 'zone'.

Steps to reproduce

The failure is gone if I do either change below

  • limiting the provider version to 6.42.0
  • providing region field at provider block

Important Factoids

No response

References

No response

b/431079161

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions