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
Extend the set of command-line flags returned by /v2/info #5612
Conversation
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.
I'm building your change at jenkins-marathon-pipelines-PR-5612-1.
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.
✔ Build of #5612 completed successfully.
See details at jenkins-marathon-pipelines-PR-5612-1.
You can create a DC/OS with your patched Marathon by creating a new pull
request with the following changes in buildinfo.json:
"url": "https://s3.amazonaws.com/downloads.mesosphere.io/marathon/snapshots/marathon-1.5.1-17-gef3e93e.tgz",
"sha1": "aff4c3e8273577cd21f885e431f850a1b52aad0a"
\\ ٩( ᐛ )و //
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.
model these new fields in RAML ... ?
@alenkacz why do you think it would be nice to do? |
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.
if it is not that thing in RAML (https://mesosphere.github.io/marathon/api-console/index.html) then OK
I agree with @alenkacz. For master we have to add the fields to the RAML. However, they do not exist for 1.4 and 1.5. |
@jeschkies I don't get what the benefit is of having a RAML type for JSON objects returned by |
No description provided.