Getting foreman-maintain on Debian is now a priority for me. Some work towards that goal was already merged there are some existing patches waiting on review but some parts are still completely missing so I have no time estimate at the moment (expect weeks).
As for fp-curl in foreman-maintain for me the important question is what UX that would provide. I can see the benefits of having everything at one place with unified interface, possible checks the proxy is up etc. On the other hand
fp-curl /features looks more convenient then
foreman-maintain proxy api /features.
It is worth mentioning that the code parsing
settings.yaml and extracting the connection details is already in foreman-maintain as we already talk to the proxy are reading features etc. I wanted to suggest to have fp-curl in proxy let it do the hard work and use it in foreman-maintain but as we have to support older Foreman and Satellite versions in foreman-maintain the code will have to remain.
As Sean mentioned foreman-maintain should provide more comfort for the user so I assume we should have the frequent proxy calls predefined and with human readable output e.g.
foreman-maintain proxy features. I don’t have problem with
foreman-maintain proxy api for arbitrary API call being part of them.