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 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:
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
OS Redhat8
TF 1.4.6
AWS provider 4.16.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: