-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade go-marathon to 15ea23e. #1635
Upgrade go-marathon to 15ea23e. #1635
Conversation
ac59149
to
98f1f4d
Compare
|
Interesting. I wonder why the mock fails now but did not do on the last go-marathon upgrade, which is ~2 commits behind and no API changes were introduced in the meantime AFAIR. Will take a look. Thanks, @ldez! |
// GetAppOpts contains a payload for Application method | ||
// embed: Embeds nested resources that match the supplied path. | ||
// You can specify this parameter multiple times with different values | ||
type GetAppOpts struct { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem is here
98f1f4d
to
c514def
Compare
Fixed, thanks to @ldez and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Marty 😃
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @timoreimann !
LGTM :)
Our vendored copy contains a bug that causes unavailable Marathon nodes to never be marked as available again due to a misconstruction in the URL to the Marathon health check / ping endpoint used by go-marathon internally. A fix[1] has been published. [1]gambol99/go-marathon#283
c514def
to
9aeffdf
Compare
Our vendored copy contains a bug that causes unavailable Marathon nodes to never be marked as available again due to a misconstruction in the URL to the Marathon health check / ping endpoint used by go-marathon internally.
A fix has been published.
Targeting 1.3 since the impact on a production deployment could be quite severe: For long-running Traefik instances, it only takes as many failed attempts to reach the Marathon API endpoint as there are Marathon nodes in the cluster for the Marathon provider to stop working properly.