-
Notifications
You must be signed in to change notification settings - Fork 170
Chef Export no longer includes files outside of CookbookVersionLoader segments such as test/ or spec/ #709
Comments
What kind of other files do you need? It's more likely that we'll solve this at the |
In our particular case, our cookbooks expose integration tests so that those tests can be run by downstream cookbooks. This is particularly helpful for policy-level acceptance & integration testing. See test-kitchen/test-kitchen#843. Though I could imagine a use-case for any non-standard cookbook repo layout, for whatever reason. I would also argue that this issue should be categorized as a "bug" rather than "enhancement" - in the previous release of ChefDK (0.10.0), the |
The plan is to fix this via chef/chef#4629 The end result would be that everything that isn't either explicitly ignored or contained in a dotdir at the cookbook root would be exported (see the pull request and code comments therein for more about that). If you specifically want |
I see what you're saying now - yes, there's a difference between adding support for |
I put up a PR for this here: #716 Will be on vacation next week, but I will look into it after if no one finishes that up. |
ChefDK::PolicyfileServices::ExportRepo
calls out toChef::Cookbook::CookbookVersionLoader
, which hardcodes a whitelist of files and folders, in order to determine what files to upload to a testkitchen box. This prevents other files and folders in a cookbook from being uploaded. Other kitchen provisioners provided by testkitchen use thecookbook_files_glob
kitchen configuration option to control what files will be uploaded, but thepolicyfile_zero
provisioner doesn't even look at this config option, instead relying completely on CookbookVersionLoader to figure out what to upload.The text was updated successfully, but these errors were encountered: