You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2022. It is now read-only.
When marathonctl app create fails for some reason other than the application already existing (status code 409) or the proposed ID being invalid (status code 422), marathonctl doesn't display any of the detail provided by the server to clarify what went wrong, per the comments in file app.gohere.
At minimum, marathonctl should show the content of the response object's "message" field, and perhaps the other errors associated with each path in the "details" collection.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When marathonctl app create fails for some reason other than the application already existing (status code 409) or the proposed ID being invalid (status code 422), marathonctl doesn't display any of the detail provided by the server to clarify what went wrong, per the comments in file app.go here.
At minimum, marathonctl should show the content of the response object's "message" field, and perhaps the other errors associated with each path in the "details" collection.
The text was updated successfully, but these errors were encountered: