Tero Marttila

The implementation of `--platform` in the cloud plugin looks much more reasonable: https://github.com/kontena/kontena-plugin-cloud/blob/e68198337c41678f981811b5ea40c622e055c10f/lib/kontena_cli_plugin.rb#L12-L15 ```ruby option '--platform', 'PLATFORM', 'Specify Kontena Cloud platform to use' do |platform| config.current_master = platform config.current_grid =...

> Looks like our spec_helper swallows SystemExit and makes the specs pass instead of failing > > Without the rescue SystemExit it will end running the specs and say "success"...

Making this and #3278 work for `kontena stack start/stop/rm` => `StackDeploy` is going to be interesting. Can we get rid of the `StackDeployWorker` and also fix #2311 at the same...

The `ServiceHelpers#wait_for_deploy_to_finish` refactoring to remove the useless `token` argument broke the app plugin. I don't think I want to try and fix the app plugin, so I'll just revert that...

Note that at this point there is no longer any difference between `kontena service start/deploy` => `POST /v1/services/.../{start,deploy}` => `GridServices::Start/Deploy`, except that `kontena service deploy` takes the optional `--force` option...

Merged #3299, no longer WIP

You can consider using `network_mode: host` instead of published ports, if you're okay with exposing any and all ports that the service listens on, and only running one of those...

Not sure if creating opto variables that are literally called `foo.bar` is the right design here. ATM all of the child stack variables even end up getting POST'd to the...

#2504 implements `kontena node create`, `HostNode.token` websocket RPC `Kontena-Node-Token` authentication. In addition, this also needs plugin changes for provisioning support.

#2504 is now merged, and provides agent/server support for per-node tokens, including CLI commands to manage them. I'm keeping this issue open to track the Kontena plugin changes to use...