Walter Dolce
Walter Dolce
> Edit: looks like you're correct, we are using the beta version within that resource [...] Yep. That's exactly what I was referring to :-) I should have added a...
That's good to know. I guess that's the usual "versioning enigma".
FYI I have already set the `GOOGLE_APPLICATION_CREDENTIALS` environment variable pointing to my `application_default_credentials.json` file.
InSpec version in use is `0.6.0`
@skpaterson It appears I was missing the `zone` parameter in the test. With the following, it *kind of* works: ``` describe google_compute_instance(project: gcp_project, zone: 'europe-west2-a', name: 'my-instance') do ``` Result:...
This leads me to ask 2 questions: 1) Shouldn't Inspec GCP explicitly state that a certain resource parameter which is expected is missing? 2) It appears either the code or...
> For 2, so the docs read [...] Note match not eq. Of course! Silly me. Thanks for pointing that out @skpaterson :) I guess we'll leave this issue open...
I'm having the very same issue on one of the machines I work from. The user from which I run `bundle exec kitchen list` (which fails) triggers `sudo -E docker...
FYI (Please note I purposefully removed `>> {NIL|/dev/null}`) ``` $ bundle exec kitchen list -l debug D [local command] BEGIN (sudo -E docker 2>&1) sudo: no tty present and no...
In order to overcome the above, I had to do the following, which less than ideal 😅 : ``` # kitchen.yml --- lifecycle: pre_converge: - local: | sed -i ''...