-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Terraformer error importing google_comput_instance with terraform-provider-google #15059
Comments
@edwardmedia That is just a normal |
I would normally agree with you, but look at the lines 23-33 of the attached logs:
The tool informs that the error it encounters is relatable to the provider more than the tool itself. |
@Kavuti can you share the config and detailed steps you used for your testing? |
@Kavuti is this still an issue? |
@Kavuti closing this assuming it is no longer an issue. |
The issue still exists. I was trying to downgrade versions of terraformer and nothing changes. The only thing is changed for me - google cloud provider got upgraded. |
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. |
Community Note
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 tohashibot
, a community member has claimed the issue already.Terraform Version
0.13.6
Affected Resource(s)
I'm actually using Terraformer to import a manually created instance.
Terraform Configuration Files
providers.tf
Panic Output
https://gist.github.com/Kavuti/7fb0b2dfbe375a7830aa27e93eb6e359
Expected Behavior
I would expect that Terraformer would import correctly the compute instance.
Actual Behavior
Terraformer returns an error in the logs and declares that it should be reported to the provider developer.
Steps to Reproduce
tfenv use 0.13.6
terraformer import google --resources=instances --regions=your-region --projects=your-project
The text was updated successfully, but these errors were encountered: