-
Notifications
You must be signed in to change notification settings - Fork 102
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
Issue with #25
Comments
Hmm. I think this might happen even if you specify it in the run_list itself, too. I have a fix in master (commit 8d76496). Can you sync, rake install, and try out that version? |
@jkeiser master works for me 😄 |
@sethvargo just so I understand, did it fail before? |
@jkeiser that I don't know. I can confirm it's working on master, but I never tried before (I try not to do version locking that way, so I never encountered it) |
It works with the master (commit 8d76496). Do you have an estimate for the next version release? |
Soon. I want to get some chef-pedant tests written for the case, but if you have a need for a new version Right Now I can release and add the chef-pedant tests after. |
It would be appreciated if you can release a patch, but I don't want to pressure you to deviate from better practices. |
I went ahead and released 1.5.4. I still need to get tests in for this, but don't want to block anyone in the meantime. |
Thanks John. |
When I use a role to define a run_list specific for an environment and pin the cookbook version, I get the following error when I execute
chef-client
This seems to happen if we have a role specifying the version of the cookbook for an environment. For example:
This issue went away when we would change
"recipe[cookbookName::recipeName@0.1.1]"
to
"recipe[cookbookName::recipeName]"
Please let me know if you need more information.
The text was updated successfully, but these errors were encountered: