Alternatives to include external configurations(like automations.yaml)

Need some help!!

Is there any alternative way to include external files like automations.yaml into configuration.yaml file.

Current structure allowed in configuration is like:
automation: !include automations.yaml

But for some reason I am not able to use this syntax in yaml.
Can anybody suggest if there is any other way to specify include files through config.

Thanks.

Here are the docs on splitting the config. What exactly are you trying to do?

1 Like

Please define what you mean by this statement?

All you have to do is type it in to the file with your keyboard, there’s no magic to it.

Actually I am trying to create this entry dynamically through a script, and for this when I update this entry in configuration.yaml it comes with quotes… like this:
automation: ‘!include automations.yaml’

Because of these quotes around it the configuration is failing on config check.

Then you need to modify your script to not put quotes around the output.

1 Like