How to ensure that config file exists before running augeas against it
I noticed that augeas automatically creates a config file even when it does not exist. Since puppet does not enforce order it is quite possible that a config file could get created when a package does not exist. If ever that package gets installed the config file will probably get installed as '.rpmnew' and the config file created by augeas may only have a small subset of configurations in it. How can we ensure that augeas does not create a config file but only edits an existing one?