Closed bodiug closed 8 years ago
It appears that marathon 1.1.1 returns a response on /v2/deployments
that does not match its own documented spec.
To be more specific, the steps
fields in https://mesosphere.github.io/marathon/docs/rest-api.html#get-v2-deployments which is implemented by https://github.com/gambol99/go-marathon/blob/master/deployment.go#L31 cannot be populated by the response of marathon
"steps":[{"actions":[{"type":"StartApplication","app":"/foo"}]},{"actions":[{"type":"ScaleApplication","app":"/foo"}]}]
We've got the same. Looks like it's related to changes to Marathon API responses that are not reflected in the provider yet.
It's actually a bug in Marathon itself and fixed upstream already. ;)
@guidob Are you still running into this on the latest marathon?
@adamdecaf it's broken on 1.0 to 1.1.1. Still waiting for an upstream release with the fix. :|
This is now working again after upgrading to terraform 0.7.3, marathon 1.1.2 and re-compiling terraform-marathon-provider.
Since upgrading to Marathon release 1.1.1 I'm getting the following error from terraform:
The .tf files were not changed and worked fine before.