Impossible specify memcache_parameters for google_memcache_instance

[ermakov-oleg]

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 the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

terraform -v
Terraform v0.12.28

Affected Resource(s)

• google_memcache_instance

Terraform Configuration Files

resource "google_memcache_instance" "instance" {
  provider = google-beta
  name = "some-name"
  region = "europe-north1"
  project = var.project_name
  

  node_config {
    cpu_count      = 1
    memory_size_mb = 2048
  }
  node_count = 3

  memcache_parameters {
    params = {
      "listen-backlog" = "2048"
      "max-item-size" = "8388608"
    }
  }
}

Debug Output

https://gist.github.com/ermakov-oleg/3c28d81ca0e8e10bce3fe31e04995cd8

Expected Behavior

parameters for memcached were applied

Actual Behavior

Error creating Instance: googleapi: Error 400: Invalid JSON payload received. Unknown name "memcacheParameters" at 'resource': Cannot find field.

Steps to Reproduce

1. terraform apply

References

• Add memcache instance. GoogleCloudPlatform/magic-modules#3593

[ermakov-oleg]

@megan07 When can I expect to release a version with this fix?
This issue is also relevant in version 3.30.0

[megan07]

Hi @ermakov-oleg! It looks like it missed the cut-off for 3.30.0 by one day, so it should be available in 3.31.0.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!