Issue #6497 has been updated by Nigel Kersten. Status changed from Needs Decision to Accepted Assignee deleted (Nigel Kersten)
---------------------------------------- Feature #6497: Module tool should have a workflow for strictly local use https://projects.puppetlabs.com/issues/6497 Author: Randall Hansen Status: Accepted Priority: Normal Assignee: Category: Target version: Keywords: Branch: Affected URL: Here's the workflow we've been using in training: $ puppet-module generate randall-foo $ mv randall-foo foo $ rm foo/metadata.json It seems like this workflow exists because the tool assumes the target for the module is the Forge, when in fact often it's local. Copying a local module to the Forge should be a separate task, and a local-only workflow shouldn't be concerned with it. I think there's a good argument that this local-only workflow should be the default. This may require changing the "upload to Forge" workflow. -- 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.
