https://bugzilla.redhat.com/show_bug.cgi?id=2283798
--- Comment #2 from Joshua Noeske fedora@joshuanoeske.de --- I think I do not have a perfect solution for that. But I guess that many users will expect that changing the corresponding configuration option in the config file does actually change something. Moreover, when migrating from redis, it might also be desirable to keep the socket and pid file at the same place as the old ones.
In my opinion, there should at least be a warning/info somewhere that mentions that the corresponding options in the config file are useless, pointing users to /etc/sysconfig/valkey. But in my opinion, the superior option is to actually make the option useful again.
What are the arguments against `sed`-ing the config? The only one I can imagine at the moment is that changes have to be monitored to change the sed config in case there are relevant changes upstream. But I would argue that changes to the location of socket and pid files are rather uncommon. But if there are more problems with it, please tell me.