The default behavior for Filebeat modules is that all filesets are enabled by default. This puts a burden on users of modules when they upgrade versions. When a new fileset is added this is a breaking change to the end-user because they must take some action to change their configuration in order maintain the same behavior.

For example, when we add a new fileset to AWS module the end-user must add the new fileset to the configuration file just to disable it. If they don't then they will end up with errors because configuration is required for the new fileset to function.

A similar problem also manifests itself to users of the CLI when trying to enable particular filesets of a module. They get all filesets enabled by default. If they want to enable a subset of filesets they must use a wildcard option (that's undocumented AFAIK) -M aws.*.enabled=false.

My proposal is to change the default behavior of filesets to disabled by default when they do not appear in the configuration.