Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BLOCKER: Increase terraform-plugin-sdk to 2.11.0 to unlock 4Mb limit to 256Mb #732

Closed
NargiT opened this issue Aug 23, 2023 · 0 comments · Fixed by #733
Closed

BLOCKER: Increase terraform-plugin-sdk to 2.11.0 to unlock 4Mb limit to 256Mb #732

NargiT opened this issue Aug 23, 2023 · 0 comments · Fixed by #733

Comments

@NargiT
Copy link
Contributor

NargiT commented Aug 23, 2023

Terraform Version

terraform -v
Terraform v1.5.5
on linux_amd64
+ provider registry.terraform.io/pagerduty/pagerduty v2.16.0

Affected Resource(s)

All, this concerns an indirect dependency that was fixe by terraform core team already.

The source of the problem
hashicorp/terraform-plugin-sdk#650
The PR that solve this problem
hashicorp/terraform-plugin-sdk#857
The CHANGELOG of version 2.11.0

plugin: Increased maximum gRPC send and receive message size limit to 256MB (hashicorp/terraform-plugin-sdk#857)

Output

....
2023-08-23T09:42:16.0392452Z The plugin returned an unexpected error from
2023-08-23T09:42:16.0392622Z plugin.(*GRPCProvider).PlanResourceChange: rpc error: code =
2023-08-23T09:42:16.0392809Z ResourceExhausted desc = grpc: received message larger than max (4771020 vs.
2023-08-23T09:42:16.0392882Z 4194304)
....

Expected Behavior

What should have happened?
Normal run without any ResourceExhausted error

Actual Behavior

What actually happened?
Error is raised and block terraform plan

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. tf files with a Schema > 4mb
  2. terraform apply
  3. Error is raised (check out other provider with same issue grpc: received message larger than max hashicorp/terraform-provider-local#28 (comment))

Important Factoids

Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?

We have a higher (+1000) route limit for the new orchestration.

References

This repository already started work

Bumping currently terraform-plugin-sdk to 2.11.0 will fix the problem

@imjaroiswebdev maybe you could help on this one ?


This issue was created with the help of @drewboswell

@NargiT NargiT changed the title Increase terraform-plugin-sdk 2.11.0 to unlock 4Mb limit to 256Mb BLOCKER: Increase terraform-plugin-sdk 2.11.0 to unlock 4Mb limit to 256Mb Aug 23, 2023
@NargiT NargiT changed the title BLOCKER: Increase terraform-plugin-sdk 2.11.0 to unlock 4Mb limit to 256Mb BLOCKER: Increase terraform-plugin-sdk to 2.11.0 to unlock 4Mb limit to 256Mb Aug 23, 2023
imjaroiswebdev added a commit that referenced this issue Aug 24, 2023
bump terraform-plugin-sdk/v2 to solve #732
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant