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 #3771

There should be a general way to select subsets of the catalog

Added by Luke Kanies almost 6 years ago. Updated over 3 years ago.

Status:AcceptedStart date:05/14/2010
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Affected Puppet version:0.25.4 Branch:
Keywords:

We've Moved!

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


Description

We currently have ‘—tags’ for selecting portions of the catalog, and people are talking about adding —resource and —stage. We’ve also got requests for one-off portions of the catalog that rarely if ever get run again.

It’d be nice to have some kind of generalized framework for determining what aspects of the catalog should be run.

I don’t know what this would look like, but the fact that we’ve got three proposed commands right now, with probably more waiting in the wings, means that we’re probably missing some larger picture.


Related issues

Related to Puppet - Feature #3760: Support one-off or single run manifests Needs More Information 05/12/2010
Related to Puppet - Feature #3709: puppetd -t --resource 'File[/tmp/jojo]' ? Accepted 05/03/2010
Related to Puppet - Feature #3746: puppetd --tags should support logical not Duplicate 05/07/2010
Related to Puppet - Feature #4051: --tags should also apply to resources that a tagged resou... Accepted 06/21/2010
Related to Puppet - Feature #1107: Allow exclusion in tags specified on the command line Accepted
Duplicated by Puppet - Feature #4634: Add puppet agent --filter Rejected 08/26/2010

Also available in: Atom PDF