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

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Feature #7585

Make pluginsync true by default

Added by Cristian Ciupitu almost 5 years ago. Updated about 4 years ago.

Status:DuplicateStart date:05/19/2011
Priority:LowDue date:
Assignee:Nigel Kersten% Done:

0%

Category:plug-ins
Target version:-
Affected Puppet version:2.6.8 Branch:
Keywords:

We've Moved!

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


Description

Please make pluginsync true by default. I wasted a couple of days trying to figure out why a MySQL module wasn’t working because of this. I agree that I should have read more of the documentation, but it wouldn’t hurt to use more reasonable defaults and let power users disable it if necessarily.

I’m using puppet-server-2.6.8-1.fc14.noarch and puppet-2.6.8-1.el5.


Related issues

Duplicates Puppet - Feature #5521: pluginsync should be defaulted to true Closed 12/12/2010

History

#1 Updated by James Turnbull almost 5 years ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Nigel Kersten

#2 Updated by R.I. Pienaar almost 5 years ago

+1 to this, but only if the error on failure to pluginsync can be made into a info/warning with better text explaining whats going on

#3 Updated by James Turnbull almost 5 years ago

RI – which particular error do you mean? Just so I know/are reminded … is there an existing ticket?

#4 Updated by R.I. Pienaar almost 5 years ago

James Turnbull wrote:

RI – which particular error do you mean? Just so I know/are reminded … is there an existing ticket?

err: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from source(s) puppet://foo.domain.com/plugins

Not sure if there’s a ticket – recall a long internal mail thread recently

#5 Updated by James Turnbull almost 5 years ago

Oh that one. Where it fails if pluginsync is on but no lib directories exist anywhere in your modulepath.

I’ll fix that tonight – its been on my “this is fucking annoying” list for some time. Can’t find a ticket oddly.

#6 Updated by Nigel Kersten almost 5 years ago

Given the power of pluginsync, in that you can use it to deploy providers that override the ones shipped by the Puppet core or even override other Ruby libraries core code might use, do you think it’s still correct to default to true?

#7 Updated by Cristian Ciupitu almost 5 years ago

I look at modules before using them and I also think that a proper module should warn about this, although on the other hand I admit that a lot of modules don’t provide too much documentation.

#8 Updated by Andrew Forgue almost 5 years ago

Duplicate of #5521

#9 Updated by Nigel Kersten almost 5 years ago

  • Status changed from Needs Decision to Duplicate

Heh. and I didn’t raise these concerns in the original…. let’s do it.

Also available in: Atom PDF