Describe the enhancement:
We are trying to modularize all of the configurations as a standard. As per the https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-configuration-reloading.html link . I couldn't find a precise way of doing this for outputs for filebeat, so my guess work was to

# Put the below config into auditbeat.yml
filebeat.config.outputs:
  enabled: true
  path: ouputs.d/*.yml

And created an ouputs.d directory and put a my_ouputs.yml file in outputs.d.
But this doesn't work. As per community,

Currently Filebeat only allows external configuration files for modules and inputs. Moving your output configuration to an external configuration file is not supported.

Describe a specific use case for the enhancement or feature:
As per the details in the community forum, https://discuss.elastic.co/t/how-to-load-external-configuration-file/228757 an enhancement request would be truly useful to modularize the config files to send to various destinations.

Filebeat (or really any Beat) can only have a single output. By contrast, Filebeat can have multiple inputs and/or modules. So moving those to external configuration files might make more sense than for a single output. But this is more just an opinion; I think if you can make a strong enough case for this in your enhancement request issue and there's interest from other users in the community as well, we'd definitely prioritize it!