-
Couldn't load subscription status.
- Fork 126
Closed
Description
When I start the daemon, the config file which sets up my routers gets overwritten, enforcing a particular order of statements. Since I'm managing all my config file centrally (via Ansible in my case), I'm seeing constant modifications because my centrally-manged config file has a structure which better fits my needs:
- I start with defining the target's connection details -- hostname, username, password, etc
- then I specify which collectors to use
I have not tried this, but I think this config overwriting will also mangle any comments, if used. Generally, I think it's better if a daemon doesn't write to its own config file.
Metadata
Metadata
Assignees
Labels
No labels