Note, 3.18.0 brought support for loading $(sys.workdir)/data/host_specific.json. While not directly related to this ticket about what log level the messages should be if a requested augments file does not exist it does provide a way to define host specific data which is what the original description illustrated by loading Augments based on fully qualified host name.

Ping , thoughts about log level or ability to suppress messages when augments listed in the augments key are not present?

My first instinct is that they should remain errors, I think they are useful, but I can also see how they would be annoying if any of these data sets are optional. So, a workaround would be to have some policy that made sure those files existed as empty objects, and then you could still have a copy_from to keep them in sync with some upstream source leveraging missing_ok copy_from body attribute.

, thoughts about changing these errors to inform or verbose or having some way to suppress them?

Or support autoloading json files in see:

• https://tracker.mender.io/browse/CFE-2790

I am testing multiple augments setup and the files are not yet in place:

Would also be nice that the augments files are also relative to this directory: '-f ./'