v2.1 client not granting signature against workflow v2.0.0 about workflow-cli HOT 2 CLOSED

I think this is exactly the reason why we decided to put that big fat warning in there. The client is not guaranteed to work with older releases, and we highly recommend upgrading in lock-step, but occasionally older clients can be used to talk to newer servers since the API shouldn't change significantly.

That being said, I don't see any reason why this would be broken according to deis/controller@v2.0.0...v2.1.0. The only relevant change I've seen server-side is in deis/controller@46829d3 and that was in 2.0.0-alpha, so I'm at a loss how a 2.1 client would fail to save the token from a 2.0 server. I'll see if I can replicate :)

from workflow-cli.

Ok. I figured out the problem.... I screwed up 😦. When the request returns a version mismatch, it returns that error in addation to the response. When the methods get the error response they immediately bail out and don't attempt to parse the body.

The CLI on the other hand, checks to see if the error is an API mismatch, and if there is, recognizes it is a warning and continues on, even though they're only working with a blank object.

What the SDK should do is implement a method similar to the workflow-cli's checkAPICompatibility which checks if the the error is an api compatibility one before bailing out.

from workflow-cli.