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
driftctl hangs. #1653
Comments
Yep, I am having the same issue. Thanks for bringing up this issue. Edit: I just found out that regardless of local state file or s3 backend my driftctl command hangs for 15+ minutes right after scan output and then exit out with exit code 1. Last edit: Finally after reading the entire driftctl document figured out that disabling telemetry data fixes hang and timeout issue. Driftctl v0.39.0 |
Hi!
When i run a scan againt s3, driftctl hangs, so i have to kill -9 on it. And i do not get any info from debug:
Scan duration: 52s Provider version used to scan: . Use --tf-provider-version to use another version.
If i wait for 10min then it finishes.
But when i run a scan locally it doesn't hang, and the debug shows me the following:
Scan duration: 11s Provider version used to scan: . Use --tf-provider-version to use another version. DEBU[0013] Closing providers DEBU[0013] Closing provider key=aws DEBU[0013] Closing gRPC client alias=eu-north-1
The text was updated successfully, but these errors were encountered: