-
Notifications
You must be signed in to change notification settings - Fork 144
inspec-gcp not working in kitchen-terraform v5.0 #351
Comments
Hello again, @tdsacilowski! How did you detemine that the lack of InSpec 3's support for With respect to InSpec 4 and inspec-gcp, inspec-gcp is apparently not yet compatible. 😢 I've opened inspec/inspec-gcp#153 to request support for InSpec 4. |
Hi Aaron, wrt the And to clarify, I only had one And thanks for the heads-up on inspec-gcp not being yet compatible with inspec 4. Wasn’t sure how to tell if it was or wasn’t. (And now, reviewing inspec/inspec-gcp#153, I see that it’s pinned to inspec 3) For now I’ll move back to kitchen-terraform 4.9.0. Thanks! |
I think I have things pretty well pinned down (hah!)
Enter the container
Edit the Dockerfile to move to
Enter the new container:
The only downside to this workaround is that |
@bgeesaman thank you for the investigation! This definitely helps to clarify the problem. |
I believe I have identified the issue. While rbnacl is intsalled,
After installing libsodium-dev in the container, |
Can some one please verify if this branch solves the issue? #358 |
I can confirm both solutions work for me:
Thank you, Aaron! |
Hi all. I'm working on building out some tests against resources being built by Terraform in GCP. I had been using KT v4.9.0 and I was able to make use of
inspec-gcp
:My
Gemfile
:My
kitchen.yml
file:My
inspec.yml
file:My results:
However, my
local
tests were being skipped due to thehost
resource seemingly not being supported on MacOS X. Digging through inspec updates, seemed thathost
is supported on MacOS X, but in version 4, so I decided to try to upgrade kitchen-terraform to v5.0 since it updated inspec to version 4.My
gemfile
:No changes to
kitchen.yml
andinspec.yml
.My results:
Log output:
Not sure if this is a bug or if I need to alter my configuration. Can't seem to figure out the root issue here.
As a side note, updating to KT v5.0 (inspec v4) doesn't seem to help with my
host
resource issue so I'll likely need to spin up a Vagrant box running Linux to test this:The text was updated successfully, but these errors were encountered: