1.0.4 version is not able to identify the encryption properties

[vrbcntrl]

Hi @eerkunt,

I was testing the encryption_at_rest.feature with AWS RDS Instance and found that the rule is able to read the aws_db_instance resource however its not able to read the storage_encrypted=false property. it says : Failure: Resource aws_db_instance.default does not have encryption enabled (storage_encrypted). even though I have that property configured in my out file.

`. Running tests.
Feature: Resources should use encryption at rest while they are created # C:\Training\cloud\terraform-compliance\1.0.4\terraform-compliance-master\example\example_01\aws\testing-inprogress\encryption_at_rest.feature
In order to improve security
As engineers
We'll enforce encryption at rest

Scenario: RDS instances
    Given I have AWS RDS instance defined
    Then encryption must be enabled
      Failure: Resource aws_db_instance.default does not have encryption enabled (storage_encrypted).`

I have attached the .tf , .out, and .out.json files for yur reference

aws_db_instance_encryption.zip

[eerkunt]

After checking and re-testing on my local, it is working as intended.

"storage_encrypted": false,

in your plan out, therefore encryption is disabled, therefore the test you have described above is failing as intended.

[vrbcntrl]

you are right, its working as expected, somehow It was throwing the same Failure message when i had storage_encrypted : true yesterday, i guess it was a mistake.

also, in the older versions prior to 1.0.0, the failure message used to be different, meaning the message used to tell, what is the current value and what is the expected value also. I guess you have changed the Failure message format now which is fine...thanks!

[eerkunt]

With #101 ( and 1.0.5) now terraform-compliance shows additional information about the failure.