Skip to content

Uniqueness of hostRequirements #55

@ryyakobe

Description

@ryyakobe

Description

It seems that OpenJobDescription doesn't specify that names for different hostRequirement should be unique. Python library also doesn't enforce name uniqueness, so it's possible to create a template with 2 different host requirements for the same step that have exactly the same name:

  hostRequirements:
    amounts:
    - name: amount.sameName
      min: 1
    - name: amount.sameName
      min: 4

This seems to be error-prone and I wonder if there is a use-case for allowing the same name for host requirements or maybe the specification should enforce name uniqueness?

Metadata

Metadata

Assignees

No one assigned

    Labels

    spec/defectThis issue is a defect in an existing version of the specification.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions