Re: Possible bug: parsing/scheduling of editfiles sections in multiple cfengine scripts

[Ed Brown]

My experience with actionsequence suggests two things:

1.) Declaring actionsequences in multiple files means that your
actionsequence is basically indeterminate.  Actionsequences do not apply
per file.  If you want control over your actionsequence, it's best to
declare it only once at the top level (well, twice, update.conf and
cfagent.conf both need an actionsequence).

2.) Lines like this:

> actionsequence = ( ... copy.pre editfiles copy.post ... copy ... )

are misleading.  Once you qualify an action, you should qualify all of
them, if you care about the sequence.  The above does not mean that
using 'copy:' without 'pre::' or 'post::' will take place last.  In
fact, any copy actions without the qualifiers will take place when the
first copy action is scheduled.

hope this helps,
Ed