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
Use case: our mesos+marathon deployment supports a resource called networkBandwidth to specify the amount of bandwidth usable by the container. Our marathon supports to specify networkBandwidth as any other resource but this is not part of the upstream api.
I'd like to know if you would consider a PR adding the ability to add extra fields in the json generated from MarathonApp instances.
Use case: our mesos+marathon deployment supports a resource called networkBandwidth to specify the amount of bandwidth usable by the container. Our marathon supports to specify networkBandwidth as any other resource but this is not part of the upstream api.
I'd like to know if you would consider a PR adding the ability to add extra fields in the json generated from MarathonApp instances.
Example:
The idea would be to support the injection of a dict with any field not present in the official api.
What do you think?
The text was updated successfully, but these errors were encountered: