Well their alternative is `ssh` into the server in question and run it
there. Which, depending on the organization, they may or may not have
access to do, and also it's a terrible UX to have to leave a configuration
UI and connect to a different machine via a different protocol manually to
see the
>ATSCFG can generate configuration for arbitrary servers, right?
It can, but that's not my concern. My concern is that you don't know what
version of ORT/atstccfg is on each cache. Is TO the same version that's on
the cache? Or is it older or newer? Maybe the cache has a feature or bug
fix not in
ATSCFG can generate configuration for arbitrary servers, right? If we don't
want it to be callable from the API, then maybe it should be a TP
extension, so operators can still see generated configuration files.
On Mon, Nov 4, 2019 at 7:57 PM Robert Butts wrote:
> >If we do it right, maintaining
