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
Description
When running driftctl against a state file stored by the most recent version of the terraform aws provider (now on 5.* as of recently), driftctl complains of errors reading from the state file and fails to complete.
Could you please tell me how you solved the issue?
We gave up on using driftctl, and use a combination of AWS Security Hub controls, custom lambdas, and some other custom bits. prowler-cloud/prowler#2678 would be nice.
Description
When running driftctl against a state file stored by the most recent version of the terraform aws provider (now on 5.* as of recently), driftctl complains of errors reading from the state file and fails to complete.
Environment
How to reproduce
Create a few resources using terraform. Any one of these will fail:
aws_route_table
-> this will yield a"route": element 0: attribute "instance_id" is required
erroraws_default_vpc
-> this will yield aattributes "enable_classiclink" and "enable_classiclink_dns_support" are required
errorPossible Solution
Update to the most recent version of the terraform state file parsing library from hashicorp.
The text was updated successfully, but these errors were encountered: