Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-2509

Avoid changing custom resource status because of HashSet ordering

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.6.2.GA
    • None
    • None
    • None
    • False
    • False
    • Undefined

      When adding the warnings about deprecated fields in custom resources to conditions, we use currently HashSet to store them. But with multiple warnings, HashSet does give unpredictable ordering and that results in the status of the custom resource constantly changing.

              Unassigned Unassigned
              scholzj JAkub Scholz
              Jakub Stejskal Jakub Stejskal
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: