host-cmds without databases
host-cmds
is one of the most popular hooks. It has one major limitation: it is not able to edit running configuration and it needs a database.
Modification of a config-file based configuration is rather easy technically. The reluctance to implement this was based on the grounds that the modified config has to be written (config-write
) or the changes would be lost after restart/reconfiguration.
This was discussed in Porto and we decided this kind of functionality would be useful for Stork. We can mitigate the concern raised above by properly documenting it and perhaps returning something in the API response that config-write is highly recommended (but not mandatory - there are valid use cases where tweaking HR data is desired to be temporary).
This is a follow-up for Stork roadmap and backlog
discussion in Porto.