WTH is !include not able to be used on a bare line?

Month of "What the heck?!"
1

I have need of taking over the default_config to disable a bunch of stuff since the categories are not tuneable via the GUI. The problem is that I want to have a nice marked up configuration and the listing all the defaults, with descriptions really bloats the configuration.yaml which I have well organized and most keys are !include <foo>.yaml to make it easily readable.

However if I do !include default_config.yaml on a line all by itself, then you end up with an error like this when checking the validity of the configuration file:

Error loading /config/configuration.yaml: mapping values are not allowed here
  in "/config/configuration.yaml", line 5, column 11

An example of the config file that I’m trying to load:

# Loads default set of integrations. Do not remove.
#default_config:
!include default_config.yaml

automation: !include automations.yaml
frontend: !include frontend.yaml
homeassistant: !include homeassistant.yaml
http: !include http.yaml
logger: !include logger.yaml
notify: !include notify.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
2

Using “include” should be like

some_dict: !include xxx.yaml

or

some_list:
  - !include xxx.yaml
  - ...
3

Yes, I’m aware that that is how it’s currently working. What I’m asking for is the ability to use it on a bare line so that I can take a large section out of my main configuration file and have it in a different one for better documentation and clarity.

4

You can include it as a package

5

Pretty certain that isn’t going to do what I want since the docs seem to read that the contents of the packages need to be namespaced.

It’s the same issue just packaged differently.

I’m trying to be able to take over the default_config: section but don’t want the entire thing sitting in my primary configuration file. This is actually related to this WTH I raised earlier.

6

No, you can do it with packages

7

Ok, this does seem to work, though the backup: declaration gets flagged. I guess I’ll mark this WTH as completed as this is a solution

8

Actually, several things aren’t working correctly when I do this. Including the logbook :frowning: so no, this is not a way to resolve this specific issue.

9

May be this can help you in using packages