As part of the process of migrating from toolforge webservice to toolforge jobs,
maybe the jobs-api should be able to retrieve and display webservices created using toolforge webservice.
This can be in read-only mode for now (basically shouldn't be able to perform any state change operations like restart, stop, delete), but the next step will be to enable toolforge job to effectively take over webservices created with toolforge webservice
I'm not sure about this, it introduces a lot of complexity and binds toolforge jobs to be backwards compatible with the internal specifics of webservice cli.
I think that for the migration we can just restart the webservice when ready (stop using the old webservice, start using jobs version of it). No need for a transition period that way, wdyt?
ok maybe it's premature to do this now, but eventually we'll need to find a way to migration legacy webservice deployments to jobs-api deployments
I'll close this for now, and start a design document on the parent to discuss and define the solutions first.