Jira (PUP-10665) Add weak dependencies to puppet resources

[Trevor Vaughan (Jira)]

Title: Message Title

Trevor Vaughan updated an issue   Puppet / PUP-10665 Add weak dependencies to puppet resources Change By: Trevor Vaughan After [a long discussion in Slack|https://puppetcommunity.slack.com/archives/C0W1X7ZAL/p1599682853112600], I was asked to create a ticket around adding 'weak dependencies' to puppet resources. Weak dependencies work like the {{wants}} keyword in {{systemd}} in that resources will be ordered after other resources that they {{want}} but failures in earlier resources will not cause cascading errors into resources that {{want}} them. This would be useful in cases like the {{yumrepo}} resource which may cascade down to packages that do not actually reside in that repository. Per the Slack discussion, it looks like implementing this in the compiler is going to be the best case for backwards compatibility and could constitute a non-breaking feature enhancement. An example of what this might look like is: {code} file { '/tmp/foo':   owner => 'root',   mode => '0640',   requires => [ File['/tmp'], Exec['foo'] ]   wants => [ File['/etc/bar'], Exec['baz'] ] } {code} In this case, {{requires}} would work as usual and {{wants}} would use the resource if present, ignore it if not, and not cascade resource failures. If something exists in both {{requires}} and {{wants}} then the stronger dependency ({{requires}}) should win. Add Comment   This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371714.1599956556000.35122.1600085400037%40Atlassian.JIRA.