Jira (PUP-6165) it should not be possible to disable manifest ordering

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on PUP-6165   Re: it should not be possible to disable manifest ordering The making of "manifest-order" into the only setting also turns it into a guarantee - if we introduce an opt-in to optimize with parallel execution that guarantee would be broken. Thus, if we do this we miss the future possibility of automatically fully optimizing the agent's time to apply a catalog by parallelizing work. Users would then need to explicitly state what can be "executed in parallel when possible". Alternatively, we could offer offer a way to place resources in manifest order sequence as if explicitly joined by relationships - that is, what you would need to do manually today in a public module if you care about the order. This could take the form of a function call performed in a class - for example: class example { resources_in_sequence() notify { 'who': message => 'I am on first': } notify { 'what': message => 'I am on second': } } or class example { with_resources_in_sequence() | | { notify { 'who': message => 'I am on first': } notify { 'what': message => 'I am on second': } } } Doing the opposite (parallel is ok) would work in analog. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.