View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006173 | unreal | ircd | public | 2022-09-30 18:51 | 2023-02-03 12:50 |
| Reporter | Valware | Assigned To | syzop | ||
| Priority | none | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Summary | 0006173: Feature request: Allow querying config items from JSON-RPC | ||||
| Description | Feature request: Allow querying config items from JSON-RPC This would be a nice feature to have because it allows other non-unrealircd servers on the network to know more about properties of the network, which paves the way for a cleaner integration, should the foreign server in question need to know. For example our conversation in #unreal-support about whois-details, it would be great to be able to quickly query this information instead of parsing the unrealircd config itself, which presents problems due to the potential to have not rehashed/applied the changes of settings, as well as only being able to parse the config local to the machine. Additionally it would be nice for all the servers to know about a single server rehash so that it may query the changes as they happen. | ||||
| Additional Information | Have a great day! | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
I'm afraid I will have to close this one due to it not being realistic. It is for the same reason that "STATS S" does not show all options. For each and every option you have to write special code. There are sooooooooooooooooooooooo many options, it is is not feasible, it would cost hundreds of hours. Hours that are better spent on other things. We could show the parsed config, though, like the ConfigEntry stuff, but that is not the same. It would be just an intermediate way of displaying the config file. I don't think that's terribly useful and you would still have to take into account the various forms of settings (and handling values like "yes" "1" etc as being the same), and having like one set::whois-details block in one place and another half of the set::whois-details being elsewhere. Etc. Etc. Nah... We can offer a way to show and/or edit the configuration files remotely via JSON-RPC. I'm not sure if that is a good idea, that would be another discussion, but that IS possible without too much effort. |
