Opened 4 years ago

Last modified 3 years ago

#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):


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.

Change History (2)

comment:1 Changed 4 years ago by trev

  • Cc trev added; palant removed

comment:2 Changed 3 years ago by fhd

  • Cc trev removed
Note: See TracTickets for help on using tickets.