Opened on 05/27/2016 at 03:23:23 PM
Last modified on 12/21/2017 at 11:29:03 AM
#4082 new change
Establish convention for denoting Puppet resource relationships
Reported by: | matze | Assignee: | matze |
---|---|---|---|
Priority: | P3 | Milestone: | |
Module: | Infrastructure | Keywords: | |
Cc: | fhd, darkue, fred | Blocked By: | |
Blocking: | Platform: | Unknown / Cross platform | |
Ready: | no | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description
Resource order in Puppet is declared in various fashion. We have learned that the various ways to achieve the same goal (irregardless whether that is a static or dynamic relationship) can lead to quite some confusion (see in particular the code-review for ticket #4073). For the sake of better insight and more clean code, we should thus establish a convention that focuses on a single way to denote relationships, ideally one that works in every situation -- in order to avoid conditionals in both code and authoring.
Attachments (0)
Change History (2)
Note: See
TracTickets for help on using
tickets.