Can someone clarify exactly how berks and kitchen interact in this scenario:
Cookbook under test: passenger_nginx_vhost_test
This is a cookbook to test an LWRP that I am writing in the cookbook
The ‘passenger_nginx’ cookbook is a dependency for passenger_nginx_vhost_test.
When I first ran kitchen converge, the Berksfile this pointed to git
which obviously lacked the LWRP, as I hadn’t written it, but once I
started working on the LWRP I updated the Berksfile to point to the
cookbook on disk:
$ grep passenger Berksfile
cookbook ‘passenger_nginx’, path: ‘/home/kitchen/passenger_nginx’
Upon running another kitchen converge, the cookbook on the test
instance was still the old one from git. I then bumped the version in
the passenger_nginx metadata and tried a converge again. Same effect.
In order to get the updated cookbook transferred to the test instance
I needed to run a manual berks update, which pulled in the newer
cookbook from disk, and was subsequently used by kitchen converge.
My expectation is that this intermediate berks update is unnecessary.
Am I missing something?
Founder, Principal Consultant,
Atalanta Systems Ltd,
Direct: +44 (0) 1329 550203
Mobile: +44 (0) 7917 101919
Atalanta Systems: The Agile Infrastructure Enablers