Feature #4051
--tags should also apply to resources that a tagged resource depends on
| Status: | Accepted | Start date: | 06/21/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.5 | Branch: | ||
| Keywords: | ||||
Description
When using —tags, puppet will run a resource without its dependencies. A resource should never be run without its specified dependencies.
file{'/tmp/one':
ensure => file,
tag => 'one',
}
file{'/tmp/two':
ensure => file,
require => File['/tmp/one'],
tag => 'two',
}
file{'/tmp/three':
ensure => file,
require => File['/tmp/two'],
tag => 'three',
}
puppet --tags three
# puppet --tags three /tmp/tags_test.pp notice: //File[/tmp/three]/ensure: created
what about /tmp/one and /tmp/two?
Related issues
History
#1
Updated by James Turnbull almost 3 years ago
- Status changed from Unreviewed to Needs Decision
- Assignee set to Luke Kanies
#2
Updated by Luke Kanies almost 3 years ago
- Status changed from Needs Decision to Accepted
- Assignee deleted (
Luke Kanies)
Should this be the default? Would you expect this to always happen, or should it be configurable with options?
#3
Updated by Alan Barrett almost 3 years ago
Please do not make this the default.
I would like to have a way to select “resources with these tags, and their dependencies”, but I need to retain the ability to select “resources with these tags, and no other resources whatsoever”. The most common reason, in my case, is that people make changes that did not go through puppet, but that nevertheless should not be accidentally overwritten by puppet.
#4
Updated by Alan Barrett almost 3 years ago
This is related to #3771
#5
Updated by Dan Bode almost 3 years ago
- Subject changed from --tags should also apply resources that a tagged resource depends on to --tags should also apply to resources that a tagged resource depends on
I would expect this to be the default, and agree that it should be configurable.