Bypass startup process with Cloud-init

Feature Requests
1

As a user who manages multiple sites (with the number constantly growing), I would like to be able to bypass the manual initialization with a startup file like cloud-init.

Currently, there is a work-around where you can restore from a generic backup, or directly modify the configuration file to skip configuration, but it would be nice to have a YAML file only consuned on the initial launch that sets up the system.

The main benefit is being able to make slight changes to a common config file that would allow an entirely new setup. For example, changinf a variable name to “Johnson” could change all of the basic naming schemes for the home, default users, etc.

2

I highly suggest you write your own integration for this, because it would never be merged into core. Like ever…

3

Absolutely agree with @Sir_Goodenough.

This is certainly a ‘fringe’ use of HA.

4

Fair enough. The only challenge is that this would need to happen before you add integrations.

How would you suggest solving that issue? Perhaps making a backup of a system with just the custom integration and using the existing restore functionality?

5

Yes. Basically, the generic backup is your best path.

So, basically, you’d need a separate instance that you keep up to date with your changes and use that.

Then, of course, customize afterwards. This will get out of hand very fast as each site customization grows.

1 Like