Use Case
A Bolt project in a control repo may require different modules than the control repo's Puppetfile. However, bolt module install and bolt module add are currently hard-coded to work on the project-level Puppetfile, with no option to change it. This is both inconvenient and inconsistent with how bolt's deployed modules are kept separately in .modules/, and configurable with the moduledir option.
Describe the Solution You Would Like
Add a puppetfile option to the bolt-project.yaml that can change the name/path of the Bolt Project's Puppetfile.
Use Case
A Bolt project in a control repo may require different modules than the control repo's Puppetfile. However,
bolt module installandbolt module addare currently hard-coded to work on the project-levelPuppetfile, with no option to change it. This is both inconvenient and inconsistent with how bolt's deployed modules are kept separately in.modules/, and configurable with themodulediroption.Describe the Solution You Would Like
Add a
puppetfileoption to thebolt-project.yamlthat can change the name/path of the Bolt Project's Puppetfile.