-
Notifications
You must be signed in to change notification settings - Fork 58
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
Add support for profiles_path #75
Add support for profiles_path #75
Conversation
Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog. GitHub Users Who Are Not Authorized To ContributeThe following GitHub users do not appear to have signed a CLA: |
Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future. |
The test failures are due to RuboCop offenses for class length and assignment branch condition. How would you like me to resolve? Here are the offenses:
|
|
Yeah, what I am trying to do is reference local profiles. Basically try to get over this error:
Some more context from me might also help. This is my ---
driver:
name: vagrant
provisioner:
name: chef_zero
verifier:
name: inspec
profiles_path: test/profiles
platforms:
- name: ubuntu-14.04
suites:
- name: base
run_list:
- role[base] And the directory structure looks like this:
|
Yeah, that is great. We will add a proper dependency resolution to inspec soon. That solves the problem in general :-) |
\0/ yay. Any idea on timeline for dependency resolution? And anything I can good to help out there? |
I assume it will become mid-may :-( |
Ok, is this the issue I should follow? inspec/inspec#533 |
@brettlangdon yes, exactly! |
Thanks, I am content if you want to close this issue, or leave open until it is resolved. Your call. |
I merge asap |
\0/ :D thanks @chris-rock |
Address #66
For this change we are adding the ability to pass through
profiles_path
from.kitchen.yml
into theInspec::Runner
.Example
verifier
for.kitchen.yml
: