Feature #8434

Expose Puppet's modulepath command line option

Added by Oliver Hookins 10 months ago. Updated 4 months ago.

Status:Rejected Start date:07/15/2011
Priority:Normal Due date:
Assignee:Nikolay Sturm % Done:

0%
Category:-
Target version:-
Keywords: Branch:
Votes: 0

Description

We test modules in clean VM environments where we place the modules in their expected final location and then want to direct cucumber-puppet to test the features stored with that module. At very least we need the modulepath to be set so that we can direct cucumber-puppet (and by extension, Puppet itself) to the correct classes involved in the feature testing. Since I don’t want to edit files in my automated tested (e.g. features/support/hooks.rb) it would be great if this were a command-line option to cucumber-puppet itself.

History

#1
Updated by Nikolay Sturm 10 months ago

  • Status changed from Unreviewed to Accepted
  • Assignee set to Nikolay Sturm

#2
Updated by Oliver Hookins 10 months ago

I’ll see if I can give you a patch for this – let me know if you are already working on it ;)

#3
Updated by Oliver Hookins 10 months ago

OK, it may not be as simple as I thought. Since there is a clear break in the middle of the execution chain of bin/cucumber-puppet –> cucumber –> cucumber-puppet support files there doesn’t seem to be an easy way to pass through the Puppet modulepath using command line arguments.

#4
Updated by Nikolay Sturm 4 months ago

  • Status changed from Accepted to Rejected

I fear you are right, the current design does not allow to pass command line options to the cucumber-puppet class.

One way to workaround this problem would be to create a file like features/support/modulepath.rb according to environment on the target machine:

Before do
  @puppetcfg['modulepath']  = '/my/puppet/modules'
end

Closing this request, as I don’t see how to fix it in cucumber-puppet.

Also available in: Atom PDF