Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

verifying via kitchen-terraform verifier #71

Closed
wyardley opened this issue Oct 30, 2018 · 4 comments
Closed

verifying via kitchen-terraform verifier #71

wyardley opened this issue Oct 30, 2018 · 4 comments

Comments

@wyardley
Copy link

Are there any examples of using the verifier with kitchen verify? Is there any clean way to do this vs. using inspec exec -t gcp:// [test]?

I threw up an issue here, but just wondering if anyone here has any context or examples on whether (and how) this is possible.
newcontext-oss/kitchen-terraform#286

@skpaterson
Copy link

Hi @wyardley, I believe this is a future enhancement, see:
inspec/kitchen-inspec#179
Feel free to comment or 👍 on there!

@adrienthebo
Copy link
Contributor

adrienthebo commented Oct 30, 2018

@wyardley a colleague provided this .kitchen.yml file; I haven't verified it but it might be worth trying out:

driver:
  name: terraform

provisioner:
  name: terraform

verifier: # https://www.rubydoc.info/github/newcontext-oss/kitchen-terraform/Kitchen/Verifier/Terraform
  name: terraform
  systems:
    - name: system
      backend: gcp
      shell: true

platforms:
  - name: k8s

suites:
  - name: verify

@wyardley
Copy link
Author

@skpaterson @adrienthebo Yes, sorry, hadn't updated here, but I did eventually get it working as reported in the other thread!

I will try to post a docs PR for this project to make it easier for people to find out how to do it.

@skpaterson
Copy link

@wyardley that would be great, thanks!

skpaterson pushed a commit that referenced this issue Jan 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants