You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the terraformer import command to reverse-engineer a Google Cloud Platform (GCP) project for Cloud SQL resources, the process fails with the error:
2024/12/23 23:47:20 exec: no command
This occurs despite:
A valid service account being used and authenticated.
Correct project and region parameters being provided.
terraformer import google --resources=sql --projects=ai-credit-product --regions=me-central2
Expected Behavior
Terraformer should import Cloud SQL resources and generate Terraform configuration files in the generated directory.
Actual Behavior
The command fails with the following error:
2024/12/23 23:47:20 exec: no command
Environment
Terraformer Version: Version v0.8.24
Terraform Installed: Yes
Operating System: Arch Linux (WSL)
Findings
The error exec: no command indicates Terraformer is unable to locate the Terraform binary.
The service account credentials are valid, and the GCP project and region are correctly specified.
Using the GCP CLI, Cloud SQL instances can be listed successfully:
gcloud sql instances list --project=ai-credit-product
The text was updated successfully, but these errors were encountered:
anqorithm
changed the title
Bug Report: Terraformer Fails to Import Google Cloud SQL Resources
Terraformer Fails to Import Google Cloud SQL Resources
Dec 23, 2024
Description
When running the
terraformer import
command to reverse-engineer a Google Cloud Platform (GCP) project for Cloud SQL resources, the process fails with the error:This occurs despite:
Steps to Reproduce
Expected Behavior
Terraformer should import Cloud SQL resources and generate Terraform configuration files in the
generated
directory.Actual Behavior
The command fails with the following error:
Environment
Findings
exec: no command
indicates Terraformer is unable to locate the Terraform binary.The text was updated successfully, but these errors were encountered: