Skip to content

Support custom fields in application definition #258

@kamaradclimber

Description

@kamaradclimber

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:

MarathonApp(
  id='incubator/demo',
  cpus=1,
  mem=128,
  ...
  extra_fields: {
    "networkBandwidth": 1000
  }
)

The idea would be to support the injection of a dict with any field not present in the official api.

What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions