Tero Marttila

Switching over to node tokens really also needs a fix for #2502 (separate weave shared secret) first.. currently each node still requires the `KONTENA_TOKEN` regardless, because it's also used as...

This isn't happening for 1.4 yet, because it also needs the changes for the separate weave secret. There's a WiP implementation of those in #2583, but it's tied up with...

Per #3100 the services using `volumes_from` no longer get re-deployed by the server, but it doesn't really matter because the agent wasn't picking the `volumes_from` changes either. I suspect that...

This PR is 98% just fixing the server specs to use realistic PEM values instead of invalid placeholders.

> It's currently not even possible to use wildcard certificate manually imported certificates as the loadbalancer stack fails with the error: [error] Psych::SyntaxError : (loadbalancer.yml): did not find expected alphabetic...

Confirm that this is some combination of alpine Linux + rspec + kommando that's causing stty to output that to stderr: ``` 1) stty outputs size Failure/Error: expect(k.out).to match /\d+...

Reported as an issue in `tty-screen`, I think it should be suppressing the `stderr` output from `stty` in this case: https://github.com/piotrmurach/tty-screen/issues/6

It only happens when running the specs in an `alpine` container, and I've stopped doing that for other reasons since. Wouldn't hurt to update the CLI deps and then get...

This happens for all errors, including 422 validation errors: ``` DEBUG Request POST /v2/stack-files: 422 Unprocessable Entity: {"errors":[{"status":422,"source":{"parameter":"server"},"detail":"key not found: \"description\""}]} [fail] Pushing test/whoami.yaml to stack registry as terom/whoami:1.0.0 ERROR...

> This may be different if you have the cloud plugin installed, it monkeypatches the error handler. Right... with `bundle exec` on git master, it actually works: ``` $ bundle...