Using packages for config splitting: ignoring folders

This gives a possibility to add ALL yaml files located inside “conf” folder (including subfolders):

homeassistant:
  packages: !include_dir_named conf

Currently to EXCLUDE some yaml file from “packaging” I change the file’s name into smth like “*.disabled”.
If I need to exclude a whole FOLDER this renaming must be done for each yaml file.

In some mediaportals like MediaPortal, Kodi there is a possibility to exclude some folder(s) from a scanning process: if a folder contains a file named “nomedia” - then this folder is excluded.

I propose to add a similar functionality into HA: if some folder contains “excluded” (or whatever) file - then this package is not used (including subfolders).

trying to figure out why you would want to exclude, but cant come up with a reason I would require any file I purposely store in the shared Packages folder to be ignored.

Could you elaborate on the why for this request?

Easy: you need to exclude some functionality.
But not forever - for today / an hour / a year.
Do not recommend disabling entities/devices/automations.

I do this now by simply moving the files to a different folder outside of conf (using your example)

This is a possible way, have to do it in some cases (when a folder includes subfolders).

P.S. Suggest to discuss particular current ways of excluding here:

This particular thread is supposed to be about FR.

Yeah me too, that’s the whole idea: need to exclude some functionality? Take it out of the packages folder…

2 Likes