The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Refactor #13642

Move "searching the forge..." notice closer to the implementation

Added by Kelsey Hightower about 2 years ago. Updated about 2 years ago.

Status:ClosedStart date:04/05/2012
Priority:NormalDue date:
Assignee:Kelsey Hightower% Done:

0%

Category:-
Target version:2.7.14
Affected Puppet version:2.7.12 Branch:https://github.com/puppetlabs/puppet/pull/627
Keywords:geordi cleanup

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

Currently the PMT search action assumes the searcher implementation will connect to the HTTP server defined by Puppet.settings[:module_repository] when searching for modules on the Forge. The server defined by Puppet.settings[:module_repository] is then used in a message printed on the console: “Searching #{server} …”. This is a little too close to the implementation and the notice should be moved closer to where the search is actually taking place.

History

#1 Updated by Kelsey Hightower about 2 years ago

  • Status changed from Accepted to In Topic Branch Pending Review
  • Branch set to https://github.com/puppetlabs/puppet/pull/627

#2 Updated by Daniel Pittman about 2 years ago

  • Status changed from In Topic Branch Pending Review to Merged - Pending Release
  • Target version changed from 2.7.x to 2.7.14

#3 Updated by Matthaus Owens about 2 years ago

  • Status changed from Merged - Pending Release to Closed

Released in Puppet 2.7.14rc1

Also available in: Atom PDF