Change Details

- Toolforge webservice start becomes an alias for “toolforge jobs run --webservice” that is similar to “toolforge jobs run --publish … webservice”, as in, the name of the webservice job is going to be “webservice”, and the default - When doing “toolforge jobs dump” you should get back an actual continuous job with the params set to the webservice defaults from image-config - We can remove then most of the logic out of it - This also means checking the status through jobs-api

We have https://phabricator.wikimedia.org/T423408 which introduced support for `--publish`, and is the actual way to handle exposing the job to the internet like the webservice. Support for this `--webservice` option is needed because `--publish` is lower level and requires the user to specify things like port, command, continuous job, etc. `--webservice` should help abstract all of that away and look more like what users are familiar with in webservice-cli. **this involves:** * adding the `--webservice` option to `toolforge jobs run` on `jobs-cli`. * specifying the `--webservice` option should call a dedicated webservice endpoint on the `jobs-api`, which handles creating the continuous job with --publish and all the webservice defaults * When doing “toolforge jobs dump” you should get back an actual continuous job with the params set to the webservice defaults from image-config * This also means checking the status through jobs-api

- Toolforge webservice start becomes an alias for “toolforge jobs run --webservice” that is similar to “toolforge jobs run --publish … webservice”, as in, the name of the webservice job is going to be “webservice”, and the defaultWe have https://phabricator.wikimedia.org/T423408 which introduced support for `--publish`, - When doing “toolforge jobs dump” you should get back an actual continuous job with the params set to the webservice defaults from image-configand is the actual way to handle exposing the job to the internet like the webservice. Support for this `--webservice` option is needed because `--publish` is lower level and requires the user to specify things like port, command, continuous job, etc. - We can remove then most of the logic out of it`--webservice` should help abstract all of that away and look more like what users are familiar with in webservice-cli. **this involves:** -* adding the `--webservice` option to `toolforge jobs run` on `jobs-cli`. * specifying the `--webservice` option should call a dedicated webservice endpoint on the `jobs-api`, which handles creating the continuous job with --publish and all the webservice defaults * When doing “toolforge jobs dump” you should get back an actual continuous job with the params set to the webservice defaults from image-config * This also means checking the status through jobs-api