Issue #10713 has been updated by Ken Barber.
I think this: #14263 covers the git installation case. If the tool would support direct integration with git, especially pointing at a branch or even master - would this cover your needs Dan? ---------------------------------------- Feature #10713: module forge (or module tool) should better support iterating on modules https://projects.puppetlabs.com/issues/10713#change-65193 Author: Dan Bode Status: Accepted Priority: Normal Assignee: Category: module tool Target version: Affected Puppet version: Keywords: Branch: This ticket was created in order to capture a user story that I was having an issue with: **high level use case:** I am using the module tool to populate modules form the forge onto my puppet deployment. I am trying to deploy multiple puppetmasters with those modules in a automated fashion. **caveat:** Unfortunately, I grabbed a module that did not support my platform. **my workflow:** * use puppet-module to download module (puppetlabs-ntp) * assign the class from a module to my node (ntp) * run the agent and discover that the module did not work * find the module's page on the forge (using the search form) * find the link to the ticketing system and file a ticket * find the link to the github repo * fork that repo into my github account (this may involve creating an account) * make the changes and commit them * get the modified version of the module to the master (this may involve installing git on the puppet master) * test the changes * submit a pull request My question is: Now what? The next time that I build out a puppetmaster, I would like it to be able to retrieve a version of the ntp module that works. If I was an external customer, this would mean waiting on puppetlabs to merge the pull request and release the module to the forge (this has historically taken weeks-months in the past) There seem to be two alternatives: * Fork the module to my own forge account * * not possible to make their modifications private * * there is no way to track which module it was forked from. this winds up increasing the number of ntp modules that exist on the forge which mean that all of the forks would be returned when future users search for ntp modules. * Use git instead of the module tool -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
