Title: Message Title
Kevin Reeuwijk updated an issue
Puppet Task Runner / BOLT-736
Give 'bolt puppetfile install' an option to not delete existing modules
Change By:
Kevin Reeuwijk
I'd like to be able to bundle my Bolt Task Plan with my application repo in a straightforward way. I've done this here for my Pipelines for Applications demo: [https://github.com/puppetlabs-seteam/PFA_NodeJS_SampleApp/tree/kevin]The Boltdir contains a Puppetfile for supporting modules and a custom 'sampleapp' module which contains my Bolt Task Plan to install all the prereqs for the application.Now ideally, my script would have just these 2 commands:{code}bolt puppetfile installbolt plan run sampleapp::prereqs{code}However if I run *bolt puppetfile install*, it will delete the sampleapp module and only install the modules in the Puppetfile.Since there is no way to use a Boltdir with supporting modules together with different modulepath that contains the module with my plan(s), I would need to make things more complicated then than desired: * publish the sampleapp module somewhere in a separate repo and put in the Puppetfile * checkout the code, run *bolt puppetfile install*, manually add the sampleapp module back in and push the code back to git.Right now I did the second option to get it working. The first option is the neatest, but I feel a simpler option should be available: {code}bolt puppetfile install --no-purge{code}This option would install the modules in the Puppetfile but not delete existing modules in the Boltdir.
Add Comment