Support for data bags in Cookbooks under test

[KAllan357]

I have some logic in my LWRP that I'd like to test that requires a data bag. Usually I would accomplish this by setting chef.data_bags_path in my Vagrantfile.

• I think Aggressively filter "non-cookbook" files before uploading to instances. #124 might mean that a data_bags directory in my cookbook-under-test will be ignored. Maybe that can be added back in?
• Add some sort of syntax to the .ktichen.yml file or just default to generating the test-kitchen Vagrantfiles with the chef.data_bags_path property set to the uploaded databags.

[fnichol]

I have some good news for you: data bags and roles are supported!

If you create a test/integration/data_bags/ directory then this will be used in your instance. Same goes for test/integration/roles/. If you have a suite called "server_only" and need special suite-specific data bags or roles, then put that data in test/integration/server_only/data_bags/ and test/integration/server_only/roles/. The more specific match will win and the shared version will be ignored.

The work in #124 will only apply to the parent directory for all cookbooks, not for other files and directories. The work underway in #128 changes strategy slightly to dump all files and directories needed for chef-* into a tmpdir before uploading everything in one shot to the instance. Data bags, roles, and encrypted data bag secret files are still supported as before.

Would it be useful to support a data_bags_path in the .kitchen.yml file in case you're pulling in data bags from another source?

Thanks!

[KAllan357]

Thank you @fnichol, this is exactly what I needed.

I'm not sure if an additional path is necessary. I'm not sure what the use case would be for that. Feel free to close this ticket.

[ekrupnik]

I do believe that a "data_bags_path" and a "roles" path would be very useful to have - this way we can simply point to a location, instead of having to copy the data_bags and roles into "/test/integration/"

[fnichol]

Excellent, @gondoi was kind enough to ship us an implementation in #161 which has landed in master! I'll close this out and please re-open if we've missed anything.

😎

[ekrupnik]

Great - the custom paths are going to be a great help! However, I am running test-kitchen version 1.0.0.alpha.7 and that code is not in that version. What version would I have to install (gem install test-kitchen -v=____ )

[fnichol]

@ekrupnik sorry, forgot to mention try: gem install test-kitchen -v=1.0.0.beta.1 or gem install test-kitchen --pre