terraformer: Getting error while running terraformer on google provider
Getting below error:
2023-04-26T05:11:12.776Z [ERROR] plugin.terraform-provider-google_v4.63.0_x5: Response contains error diagnostic: @caller=github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov5/internal/diag/diagnostics.go:55 diagnostic_attribute=“” diagnostic_severity=ERROR diagnostic_summary=“Value Conversion Error” tf_req_id=8f4a4a53-80a0-9b9a-5d77-c095be339355 @module=sdk.proto
diagnostic_detail=
| An unexpected error was encountered trying to build a value. This is always an error in the provider. Please report the following to the provider developer:
|
| Received null value, however the target type cannot handle null values. Use the corresponding types package type, a pointer type or a custom type that handles null values.
|
| Path:
| Target Type: google.ProviderModel
| Suggested types Type: basetypes.ObjectValue
| Suggested Pointer Type: *google.ProviderModel
tf_proto_version=5.3 tf_provider_addr=registry.terraform.io/hashicorp/google tf_rpc=Configure timestamp=2023-04-26T05:11:12.776Z
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 8
- Comments: 25 (1 by maintainers)
Commits related to this issue
- COS-417 - Avoid gcp bug https://github.com/GoogleCloudPlatform/terraformer/issues/1695 states that any version of the GCP provider after 4.60.0 is having an issue. Fixing the version for now. — committed to coguardio/coguard-cli by ioah86 10 months ago
- COS-417 - Avoid gcp bug (#82) COS-417 - Avoid gcp bug https://github.com/GoogleCloudPlatform/terraformer/issues/1695 states that any version of the GCP provider after 4.60.0 is having an issue. ... — committed to coguardio/coguard-cli by ioah86 10 months ago
I found that 4.59.0 is the highest “hashicorp/google” provider version that works with Terraformer as of 7/11/23.
Terraformer v0.8.24 (darwin_arm64) Terraform v1.5.2 (darwin_arm64) terraform-provider-google_v4.59.0_x5 (darwin_arm64)
I also tried with a full amd_64 stack and got the same results.
@somaz94 :
That is provider version, as below in the tf configuration (modify after export from
terraformer):Thanks @musyaf11 and @stephen-dunne I can confirm switching to GCP v4.0.0 fixes the issue for me
@sergeylanzman issue stands and is being worked on. Can anyone please remove the stale label to avoid keep alives’ noise?
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
@nicklinnell, not sure what the cause of this error, is since I even tried to change the GCP provider to 4.0.0. and it works well for me. My colleague at work also tried this and it works as well for him as well.
btw, here are the versions on my end and colleagues:
Problem exists with the 5.x providers as well
FYI, stepping back again to GCP 4.0.0 after wiping the environment worked for me !
@musyaf11 yes, I’m actually running this in a “clean” docker container the reinitialises terraform new each time it runs so there are no files other than a
main.tfcontaining:Following along as well, just started looking at terraformer for use with our google cloud DNS setup. Looks like I picked a good time to start ! 😄
Followed the steps above to wipe env. Have successfully pinned the provider to 4.60.0 as shown below but error still occurring
Also spews out the following, not sure if related
e2a: