The Puppet Labs Issue Tracker has Moved:

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 See the following page for information on filing tickets with JIRA:

Bug #18042

Deprecate face versions

Added by Josh Cooper over 3 years ago.

Status:AcceptedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Affected Puppet version: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


Versioning faces is yet another way of trying to load multiple versions of code in the same ruby runtime. The other way being environments. Since ruby does not truly support this (as Java does), we should stop pretending we support it. See #7316, #4248, #12173, #17210, #8750

When faces were created, we couldn’t install them via gems or modules. But now that we will support this in 3.0.2, we can use modules/environments or gems to manage different versions of faces, e.g. environment dev gets 0.0.2, production gets 0.0.1. I’m not sure if we just deprecate the ability to ask for a specific version, i.e. you always get the latest version, or we also deprecate versions altogether and the related code in face_collection that walks versioned directories.

Related issues

Related to Puppet - Bug #7316: puppet face applications (subcommands) delivered via modu... Closed 05/02/2011
Related to Puppet - Feature #4248: Load "library" plugins that are used by multiple puppet f... Accepted 07/15/2010
Related to Puppet - Bug #12173: Masters cannot reliably distinguish between multiple vers... Accepted 01/25/2012
Related to Puppet - Bug #17210: Updated functions are not reloaded within a worker process In Topic Branch Pending Review
Related to Puppet - Bug #8750: puppetmaster needs restart to pick up on changes in types... Duplicate 08/03/2011
Related to Puppet - Bug #18048: Multiple default actions can be created Accepted

Also available in: Atom PDF