On 9/8/14 5:20 PM, Brett Swift wrote:
> https://github.com/puppetlabs/puppetlabs_spec_helper#using-fixtures
> 
> 
> I think I'm doing it wrong. 
> 
> I'm testing a module, and specified zack/r10k in my .fixtures.yml file.
>    It complains that it can't find gcc.  I see that in the
> r10k/metadata.json file..   weird,  why isn't puppetlabs_spec_helper
> installing dependencies of my dependencies? 
> 
> I see this list that the puppet module tool takes care of for me:
> 
> └─┬ zack-r10k (v2.2.8)
>   ├─┬ gentoo-portage (v2.2.0)
>   │ └── puppetlabs-concat (v1.0.4)
>   ├── mhuffnagle-make (v0.0.2)
>   ├── puppetlabs-gcc (v0.2.0)
>   ├── puppetlabs-git (v0.2.0)
>   ├── puppetlabs-inifile (v1.1.3)
>   ├── puppetlabs-pe_gem (v0.0.1)
>   ├── puppetlabs-ruby (v0.2.1)
>   ├── puppetlabs-stdlib (v4.2.2)
>   └── puppetlabs-vcsrepo (v1.1.0)
> 
> 
> but puppetlabs_spec_helper  doesn't.    <grumble grumble>
> 
> I didn't see a ticket for this on tickets.puppetlabs.com.   Is this a
> feature request, a defect,  or  pebcak ? 
> 
> 

Hi,

puppetlabs_spec_helper does not do that. You need to specify all of your
dependencies. I would not be interested in the functionality that you
describe because as an author, I need to understand my dependencies and
to properly test them, I want to specify tagged versions in the
.fixtures.yml.

"all required modules should be listed in a file named .fixtures.yml in
the root of the project."[1]

[1] - https://github.com/puppetlabs/puppetlabs_spec_helper#using-fixtures

Best regards,
-g

-- 
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +1.206.414.8658

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/540E20FC.80600%40garretthoneycutt.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to