-
Notifications
You must be signed in to change notification settings - Fork 233
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
Value out of range on 32-bit architecture #1236
Comments
Hi @slevenick 👋 Thank you for raising this and sorry you folks are running into trouble here. Not suggesting this should be closed, but related issue for tracking: #1215 Unfortunately I need to say upfront that this should not be an issue when resources are migrated to terraform-plugin-framework, since its type system through-and-through supports 64-bit integers, 64-bit floating point numbers, and 512-bit arbitrary precision numbers if really necessary. The internals of this SDK tend to rely on the runtime architecture specific |
Ok, good to know that the plugin framework will fix it. We are still a ways away from being able to convert existing resources to the plugin framework, so any workarounds of possible fixes on the SDK would be helpful |
This looks like a blocker, is there any workaround? Upgraded GCP provider and terraform and no success. The problematic thing is: actually, there are much more ints. Also in google_bigquery_table and in google_compute_managed_ssl_certificate - certificate_id. |
Essentially a duplicate of #469 because I can't reopen. This continues to reoccur in the Google provider from time to time. For reference:
hashicorp/terraform-provider-google#15501
hashicorp/terraform-provider-google#13775
SDK version
Relevant provider source code
Terraform Configuration Files
Debug Output
Expected Behavior
Actual Behavior
Steps to Reproduce
Not entirely sure, we need to get a huge number into a resource in a 32-bit architecture. It seems to come up sometimes, but I'm not sure why exactly
References
#469 but I can't reopen it
The text was updated successfully, but these errors were encountered: